On 5 Oct 2011, at 04:46 , mattschinkel wrote:

It sounds like a great idea to me, however there has been some
resistance by some people to allow editing of their files. If a link
becomes broken and the author is not around, we would not be able to
easily edit or update the link.

I think that should be allowed. Every one has my permission to fix a link and correct textual errors, even spelling errors.

What should NOT be changed is:

- names of procedures (adding procedures is OK)
- output of procedures (returning a byte instead of a word)

in short: nothing that breaks existing code that uses this library. Another library with preferably the same procedure names is always OK, IMHO.

Maybe this can be incorporated in the Jallib Guidelines, if everyone agrees.

---
ir EE van Andel [email protected]  http://www.fiwihex.nl
Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands
tel+31-546-491106 fax+31-546-491107



Matt.

On Oct 4, 8:30 am, Eur van Andel <[email protected]> wrote:
Hi

Today I got an email from someone who wanted to use a CO2 sensor, but
couldn't find the document I linked to in my library because of,
well, linkrot.

Can the buildbot check URLs? If there is a 404, she could report it,
right? She knows the author, so she can assign blame.

---
ir EE van Andel [email protected]  http://www.fiwihex.nl
Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands
tel+31-546-491106 fax+31-546-491107

--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to jallib [email protected]. For more options, visit this group at http://groups.google.com/ group/jallib?hl=en.




--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en.

Reply via email to