And let me add that there is an activity which is not git visible and
nevertheless essential: reviewing tickets! It takes a lot of time and is
not particularly fancy (you review somebdoy else code that, most of the
time, you do not care about).
We can have something more or less automatic on trac for each author
that mixes trac activity on tickets and git activity.
On 18/09/15 11:49, Volker Braun wrote:
Most people don't write AUTHORS blocks, and don't update them if they
change anything. And why? Because its an annoying manual duplication of
what git does automatically, of course. On the other hand, it can be an
incentive for somebody to start contributing. Its still unfair and
underrepresents the regular contributors. Its also unclear to users why
only very few methods carry author information, what is our message on
those rare incidences where there is an author information? that it is a
particularly rare feat of mathematical ingenuity? Or that it was written by
somebody as his first contribution (statistically more likely)?
A better system:
* Provide a place for author's bios were everybody can write a small blurb
and link to their contribution
* Add a command that extracts and lists authorship and the recent changes
(ticket title, author, link) from git; Possibly as part of the online help
though I'd rather have online help render quick. Could be cached as part of
the docbuild process...
On Friday, September 18, 2015 at 3:09:34 PM UTC+2, John Cremona wrote:
On 18 September 2015 at 14:06, Marc Mezzarobba <ma...@mezzarobba.net
<javascript:>> wrote:
John Cremona wrote:
Just because Sage is open source does not mean that contributors
should not get credit for their work.
Of course. But from what I've seen, lots of AUTHORS sections are awfully
out of date, while the git history is a few keystrokes away...
...not to a user who types
sage: X.fancy_function?
though. Credit needs to be easily and obviously accessible or it will
not get noticed.
John
--
Marc
--
You received this message because you are subscribed to the Google
Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to sage-devel+...@googlegroups.com <javascript:>.
To post to this group, send email to sage-...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
