Closed rgaiacs closed 9 years ago
+1 to writing some sort of script, since tables in Markdown fail :-(
@gvwilson Is site/config/bootcamps_saved.yml + make contribs
reliable to be used to generate team.md
?
That's a tricky question: does someone who has helped at six bootcamps,
but never actually been an instructor, count as part of the team? What
about someone who fixed our CSS, but didn't write a lesson? But yes, I
think that instructors + make contribs
is everyone we really ought to
include.
That's a tricky question: does someone who has helped at six bootcamps, but never actually been an instructor, count as part of the team?
+1 for it.
What about someone who fixed our CSS, but didn't write a lesson?
CSS is important. Another +1.
But yes, I think that instructors +
make contribs
is everyone we really ought to include.
OK.
@gvwilson I have a prototype for site/config/bootcamps_saved.yml
+ make contribs
at https://github.com/r-gaia-cs/bc/commit/180240a110f2462557060f70ef833ba11d7dd337. How sort contributors' name?
Alphabetically by surname, please.
On Mon, Jul 07, 2014 at 02:27:08PM -0700, Greg Wilson wrote:
Alphabetically by surname, please.
Assuming the last name is the surname 1? And just the last name 2? Personally, I think figuring out a “proper” order for flat-string names is too much trouble. If we had markup allowing folks to explicitly mark which part of their name is the surname, then sorting by surname would be easy. But since that's likely too much hassle, I prefer sorting whatever the builder's locale is, ignoring even locale-specific lexicographic order [3,4].
@r-gaia-cs @wking can you please add instructions in CONTRIBUTING.md
(or wherever you think appropriate) on updating the team roster?
On Tue, Sep 30, 2014 at 11:02:32AM -0700, Greg Wilson wrote:
@r-gaia-cs @wking can you please add instructions in
CONTRIBUTING.md
(or wherever you think appropriate) on updating the team roster?
With #759 pulling the bulk of the content out into external repositories, I don't think we need to keep a central list of contributors here. I'd prefer to have just 1 as the sole central listing, and leave it to the individual lessons to list contributors however they like.
Sounds good to me - we should add a file in site
that archives all the
contributors to date so that none of that info gets lost.
On Tue, Sep 30, 2014 at 11:30:09AM -0700, Greg Wilson wrote:
Sounds good to me - we should add a file in
site
that archives all the contributors to date so that none of that info gets lost.
Or just open new issues / pull-reqeusts for each known contributor that is not listed in swcarpentry/site. No need for a repo-side listing before we add their _includes/people/ entry.
Try to address this at #767.
@gvwilson How do you want that we handle this?
That's a really good question... Harvest information across all of the repos that count as "official" Software Carpentry lessons, merge, and publish?
@wking suggested
If folks want to get on the central contributor listing (or nominate someone else to be added), I'd suggest they open an issue on swcarpentry/site [3]. If that entry was approved, I'd award the person the “creator” badge in Amy, and use Amy to list creators (and instructors, and members, and organizers) on the team page.
I like this approach.
@gvwilson I will leave you "handle" this issue, i.e., move it to Amy, move it to site or what you prefer.
Almost a duplicate of #287.
@gvwilson How do you generate
team.md
? There was a old issue when view it with small screens.I tried to address this issue before push the EPUB branch but noticed that this list has more items than the one from
make contribs
and will be better if write a script to rebuild this list when need.