|
Replies:
18
-
Last Post:
Jan 9, 2006 2:03 PM
by: jimgris
|
|
|
Posts:
3,835
From:
JP
Registered:
4/6/05
|
|
|
|
Ideas for Recognition to Build Reputation
Posted:
Jan 5, 2006 3:24 PM
|
|
Hi, guys.
We are 7 months into the project now, we are entering a new year, and I
think it's time start recognizing community members who are contributing
and participating in OpenSolaris. If you have an opinion on this, read
on ...
There's a lot going on around here. More than 10,000 people have
registered on the site, thousands are talking on the mail lists and
blogging, 33 communities have formed with another 25 or so user groups
on top of that, and people are presenting at conferences all over the
world (and we are archiving those presentations on the user group
community). Also, we've been getting a steady flow of code contributions
to the request-sponsor program, and we are recognizing those community
members here: http://www.opensolaris.org/os/bug_reports/request_sponsor/
as well as in emails to opensolaris-discuss. That's just a first attempt
at recognition, though.
So, what can we do to start recognizing more people more consistently?
And what is a reasonable list of items to recognize? Code for sure, but
we have other community members participating within
communities/projects, running user groups, going to conferences, helping
with booth duty when Sun has a big presence someplace, creating
distributions, blogging, talking to reporters and analysts, answering
questions on lists, taking pictures, making videos, writing docs,
building mirrors, working on co-development and governance plans, etc.
What else? And how do we recognize all that?
What I'd like to do is to eventually have a system where we as a
community recognize our contributors so they can build reputation over
time. I don't think we've really discussed this at length since we
opened. This is mentioned briefly in the governance draft, too, but we
don't have to wait for a full system to be in place to start the process
of recognizing people. I expect it to evolve, so why not start?
I'd love to work on this. Any thoughts?
Jim
--
Jim Grisanzio, Community Manager, OpenSolaris
http://blogs.sun.com/jimgris/
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
Posts:
1,901
From:
NZ
Registered:
6/16/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 5, 2006 6:03 PM
in response to: jimgris
|
|
Hey,
On Thu, 2006-01-05 at 15:24 -0800, Jim Grisanzio wrote:
> So, what can we do to start recognizing more people more consistently?
> And what is a reasonable list of items to recognize? Code for sure, but
> we have other community members participating within
> communities/projects, running user groups, going to conferences, helping
> with booth duty when Sun has a big presence someplace, creating
> distributions, blogging, talking to reporters and analysts, answering
> questions on lists, taking pictures, making videos, writing docs,
> building mirrors, working on co-development and governance plans, etc.
So, from a development point of view, I was somewhat surprised, having
never really looked at the ON code before, that there's no recognition
of people who wrote the code in the source files. Sure, there's probably
some Teamware logs, but that doesn't feel as public as something like a
ChangeLog [1] or author credits in the source code headers.
As to how to recognize other contributions, that's generally a much
harder thing to do - we're a community, and we're all in this together.
Any one person is as important as the next one. While the occasional
token of some free swag is a nice gesture for significant contributions,
I don't think there needs to be a formal process. We just need to be
better about praising each other on blogs/mailing lists/forums etc.
It's an amazing feeling getting a mail out of the blue saying 'Wow,
thanks - that patch/contribution you did really rocked', and that is
really one of the cornerstones of creating a fun, thriving open source
community IMHO.
Glynn
[1] http://cvs.opensolaris.org/source/xref/jds/ChangeLog for an example
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
511
From:
Registered:
3/9/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 5, 2006 11:49 PM
in response to: gman
|
|
[ ... ]
> of people who wrote the code in the source files. Sure, there's probably
> some Teamware logs, but that doesn't feel as public as something like a
> ChangeLog [1] or author credits in the source code headers.
I'm not with you on that. The Solaris sourcecode is the product of the
hard work done by so many people that putting their names into the
sourcefiles directly, or even keeping a central repository "credits.txt"
(whatever) is only going to clutter things. It puts my name into a crowd
of thousands - and definitely not at the top of things. Why should I want
that ?
For my part, I'm proud that the teamware logs reflect my work, successes
and failures (!) alike. It's a great trail of what I've worked on and how
well/bad I did on it. Almost like a mini-CV. Far more targeted and precise
than a global, huge "contributors.txt" that shows my name deep down within
a list of thousands. It makes me proud having my name appear on the v1.1
line of a history file, although so far that only happened once. It makes
me proud being able to tell someone "look at what I did" instead of just
saying "hey I'm with the crowd". There's even some pride in backout logs
followed by re-putbacks of a fixed set of changes - I failed but yet I
persisted.
A very personal opinion of mine. But since you brought it up, I just had
to speak out :)
Happy new year everyone - and may your names appear in many SCCS history
files next year !
FrankH.
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,901
From:
NZ
Registered:
6/16/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 6, 2006 2:01 AM
in response to: frankho
|
|
Hey,
On Fri, 2006-01-06 at 08:49 +0100, Frank Hofmann - OP/N1 RPE wrote:
> [ ... ]
> > of people who wrote the code in the source files. Sure, there's probably
> > some Teamware logs, but that doesn't feel as public as something like a
> > ChangeLog [1] or author credits in the source code headers.
>
> I'm not with you on that. The Solaris sourcecode is the product of the
> hard work done by so many people that putting their names into the
> sourcefiles directly, or even keeping a central repository "credits.txt"
> (whatever) is only going to clutter things. It puts my name into a crowd
> of thousands - and definitely not at the top of things. Why should I want
> that ?
I was suggesting that putting names into the source code was occasional
rather than be the norm [for example, when you create a new file],
however something like a ChangeLog, or multiple ChangeLogs are a pretty
good idea. They give a nice summary of the changes going back to the
code, and an easy to find email address for people contributing to the
code that you can contact.
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.15
I suppose in a way not unlike -
http://www.opensolaris.org/os/community/onnv/onnv_putback_logs/putbacks_20051219.html
Also remember that not everyone will initially have an account to commit
their work.
> For my part, I'm proud that the teamware logs reflect my work, successes
> and failures (!) alike. It's a great trail of what I've worked on and how
> well/bad I did on it. Almost like a mini-CV. Far more targeted and precise
> than a global, huge "contributors.txt" that shows my name deep down within
> a list of thousands. It makes me proud having my name appear on the v1.1
> line of a history file, although so far that only happened once. It makes
> me proud being able to tell someone "look at what I did" instead of just
> saying "hey I'm with the crowd". There's even some pride in backout logs
> followed by re-putbacks of a fixed set of changes - I failed but yet I
> persisted.
Maybe we just need to automatically generate a ChangeLog based on the
Teamware logs - ie. for each putback, it lists the files changed, the
putback message, name and email of the person? And ideally the putback
message will contain a reference to any contributed code.
> A very personal opinion of mine. But since you brought it up, I just had
> to speak out :)
No, that's *totally* cool - it was just a suggestion to throw out there,
on an observation that *currently* it's not very easy to see what things
are going back into ON and who is responsible for doing what.
Glynn
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
6,810
From:
US
Registered:
3/9/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 6, 2006 6:34 AM
in response to: gman
|
|
Glynn Foster writes:
> On Fri, 2006-01-06 at 08:49 +0100, Frank Hofmann - OP/N1 RPE wrote:
> > I'm not with you on that. The Solaris sourcecode is the product of the
> > hard work done by so many people that putting their names into the
> > sourcefiles directly, or even keeping a central repository "credits.txt"
> > (whatever) is only going to clutter things. It puts my name into a crowd
> > of thousands - and definitely not at the top of things. Why should I want
> > that ?
>
> I was suggesting that putting names into the source code was occasional
> rather than be the norm [for example, when you create a new file],
> however something like a ChangeLog, or multiple ChangeLogs are a pretty
I still think it looks rather cheesy. First of all, there's the plain
old clutter problem. I wasn't thrilled with the excess of the CDDL
language (the original two-line copyright notice, though slightly
annoying, was comparatively short and sweet), but a long list of
"brought to you by" attributions would just be downright obnoxious.
When I read the code, I want to see descriptions of how it works and
the assumptions it makes, not someone's CB handle, favorite pet, or
obscure quasi-political manifesto. There are times and places for all
those things, but the source to an operating system isn't one of them.
(Suggestion: write a book instead. ;-})
I think of this as being similar to littering the code with "#ifdef
notyet", "/* XXX broken */", "/* bugid 1234 */", or "/* joe at domain dot org
changed this to 7 */" trash. If it's not known to be right and isn't
actually used in the running system, yank it out. It doesn't belong.
We do need attributions for changes and historical information. It
just shouldn't pass through the compiler.
> good idea. They give a nice summary of the changes going back to the
> code, and an easy to find email address for people contributing to the
> code that you can contact.
>
> http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.15
That's exactly the sort of bad example I'd like to see us avoid, if we
can.
I'd much rather have putback logs (which show bugs fixed and files
changed in a given build), SCCS history (which shows who touched which
line in a given file for a given change), and a bug database (which
contains all the sordid history for a given bug, including how it was
evaluated, what problems might be related, and so on). The big
failing of that ChangeLog mechanism is that it's both too wordy to be
digested easily when hunting down a problem *and* too terse to explain
what happened.
And the source isn't a museum.
> Also remember that not everyone will initially have an account to commit
> their work.
That (and open access to the SCCS delta information) is the part that
really needs to be fixed. I don't think we should try to hack around
the missing parts.
--
James Carlson, KISS Network <james dot d dot carlson at sun dot com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,901
From:
NZ
Registered:
6/16/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 6, 2006 6:12 PM
in response to: carlsonj
|
|
Hey,
On Fri, 2006-01-06 at 09:34 -0500, James Carlson wrote:
> I still think it looks rather cheesy. First of all, there's the plain
> old clutter problem. I wasn't thrilled with the excess of the CDDL
> language (the original two-line copyright notice, though slightly
> annoying, was comparatively short and sweet), but a long list of
> "brought to you by" attributions would just be downright obnoxious.
Hrm, I don't think it's hugely obnoxious seeing one or two people in
some sort of Authors section - in fact I think it's pretty helpful to
see where the original motivation came from. I'm certainly not
suggesting having 100's and 100's of people. But then this is probably
not 95% of the contributions will be.
> When I read the code, I want to see descriptions of how it works and
> the assumptions it makes, not someone's CB handle, favorite pet, or
> obscure quasi-political manifesto. There are times and places for all
> those things, but the source to an operating system isn't one of them.
> (Suggestion: write a book instead. ;-})
No disagreement there. However, interestingly, it does create some sense
of the fact that there are real people actually writing this code. May
not be useful to the code, or desireable, but it does have certain
merits in a different light.
> I think of this as being similar to littering the code with "#ifdef
> notyet", "/* XXX broken */", "/* bugid 1234 */", or "/* joe at domain dot org
> changed this to 7 */" trash. If it's not known to be right and isn't
> actually used in the running system, yank it out. It doesn't belong.
Hrm, again I probably disagree with some of that - where things are
known to be broken, it's a useful reminder. And goodness knows we all
commit code that we know breaks for certain edge cases due to time
constraints, laziness or other conditions. I believe having those
reminders in the code is definitely better than lost in some putback
logs, IMHO.
> I'd much rather have putback logs (which show bugs fixed and files
> changed in a given build), SCCS history (which shows who touched which
> line in a given file for a given change), and a bug database (which
> contains all the sordid history for a given bug, including how it was
> evaluated, what problems might be related, and so on). The big
> failing of that ChangeLog mechanism is that it's both too wordy to be
> digested easily when hunting down a problem *and* too terse to explain
> what happened.
Within GNOME, usually the ChangeLog is a copy of the commit message.
ChangeLog may be a result of an inefficiency of CVS though - in that
it's not easy to track an individual commit over a number of files. With
the ChangeLog you can see what files have been changed, and consequently
go off to check the logs of those files if necessary. It may also be in
the inefficiency of CVS of not being able to look up logs off line.
> > Also remember that not everyone will initially have an account to commit
> > their work.
>
> That (and open access to the SCCS delta information) is the part that
> really needs to be fixed. I don't think we should try to hack around
> the missing parts.
Yeah, agreed - that may be more desireable.
Glynn
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
6,810
From:
US
Registered:
3/9/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 9, 2006 1:39 PM
in response to: gman
|
|
Glynn Foster writes:
> On Fri, 2006-01-06 at 09:34 -0500, James Carlson wrote:
> > I still think it looks rather cheesy. First of all, there's the plain
> > old clutter problem. I wasn't thrilled with the excess of the CDDL
> > language (the original two-line copyright notice, though slightly
> > annoying, was comparatively short and sweet), but a long list of
> > "brought to you by" attributions would just be downright obnoxious.
>
> Hrm, I don't think it's hugely obnoxious seeing one or two people in
> some sort of Authors section - in fact I think it's pretty helpful to
> see where the original motivation came from. I'm certainly not
> suggesting having 100's and 100's of people. But then this is probably
> not 95% of the contributions will be.
That's a problem, because most useful code ends up being maintained by
a fair number of people over the long haul, and this quickly becomes
page after page of "Kilroy was here."
I understand that special legal notices are a necessary evil, and that
when there's a contribution or component that has an explicit need for
attribution, we've just got no choice no matter how ugly it is in
practice, but I don't think we should be otherwise trying to determine
who gets his name in source code lights and who doesn't. It's
gratuitious and really doesn't help anyone understand the code any
better.
Helpful things include references to books or papers that cover the
algorithms, diagrams showing related data structures, lists of members
protected by locks, and other references to the code itself. It
doesn't help me in the least to know that joe at gmail dot com thought that 7
was a good number of bytes to allocate. It helps even less to know
that ucbvax!harvard!bob thought more testing was needed. I honestly
don't care.
> No disagreement there. However, interestingly, it does create some sense
> of the fact that there are real people actually writing this code. May
> not be useful to the code, or desireable, but it does have certain
> merits in a different light.
I still disagree.
I do agree that we should recognize contributors. Perhaps have a web
page listing contributors and the number of lines of changes written.
And special awards or recognition for folks who *DELETE* lines of
code.
I just don't agree that this needs to clutter the source code itself.
> > I think of this as being similar to littering the code with "#ifdef
> > notyet", "/* XXX broken */", "/* bugid 1234 */", or "/* joe at domain dot org
> > changed this to 7 */" trash. If it's not known to be right and isn't
> > actually used in the running system, yank it out. It doesn't belong.
>
> Hrm, again I probably disagree with some of that - where things are
> known to be broken, it's a useful reminder. And goodness knows we all
> commit code that we know breaks for certain edge cases due to time
> constraints, laziness or other conditions. I believe having those
> reminders in the code is definitely better than lost in some putback
> logs, IMHO.
Those are very good reasons _not_ to type "putback" in the first
place.
And when they're found, they're very good reasons to file bugs!
--
James Carlson, KISS Network <james dot d dot carlson at sun dot com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
3,783
From:
DE
Registered:
4/27/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 6, 2006 7:26 AM
in response to: gman
|
|
Glynn Foster <Glynn dot Foster at Sun dot COM> wrote:
> I was suggesting that putting names into the source code was occasional
> rather than be the norm [for example, when you create a new file],
When you like to add names into the source, you would need to do this for
External people and for Sun people in the same way.
Currently I cannot see Sun people listed in the sources......
Jörg
--
EMail:joerg at schily dot isdn dot cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
schilling at fokus dot fraunhofer dot de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
3,835
From:
JP
Registered:
4/6/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 6, 2006 1:31 PM
in response to: joerg
|
|
Joerg Schilling wrote:
>
> When you like to add names into the source, you would need to do this for
> External people and for Sun people in the same way.
Whatever we do to recognize people involved with OpenSolaris will be the
same for Sun and non-Sun community members.
Jim
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
68
From:
Registered:
12/11/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 6, 2006 2:46 PM
in response to: frankho
|
|
Frank Hofmann wrote:
> The Solaris sourcecode is the product of the
> hard work done by so many people that putting their names into the
> sourcefiles directly, or even keeping a central repository "credits.txt"
> (whatever) is only going to clutter things.
This is already being done; see "Sponsor Tasks" at:
http://www.opensolaris.org/os/community/onnv/crt/sponsor-tasks/
which says:
"Per the CDDL block text, the contributor may add a comment
/* Portions Copyright YYYY Firstname Lastname */
in the copyright section following the CDDL block at the top of the file."
See these files for examples:
http://cvs.opensolaris.org/source/xref/on/usr/src/cmd/ypcmd/ypxfrd_server.c
http://cvs.opensolaris.org/source/xref/on/usr/src/lib/libcfgadm/common/config_admin.c
In the first example, there was a two-line bugfix:
Two blocks of code were each wrapped into the conditional "if (res.status == OK)"
It was putback on 4 July 2005; along with the bugfix, the Sun copyright notice was updated from 2004 to 2005, and the line:
/* Portions Copyright 2005 Juergen Keil */
was added. For details see:
http://cvs.opensolaris.org/source/diff/on/usr/src/cmd/ypcmd/ypxfrd_server.c?r2=1.13&r1=1.12
The second example is also a two-line fix; the following lines were added:
#elif defined(__amd64)
#defineLIB_PATH_MIDDLE "/lib/cfgadm/amd64/"
It was putback on 23 June 2005; along with the fix, the Sun copyright notice was updated from 2003 to 2005, and the line:
/* Portions Copyright 2005 Cyril Plisko */
was added. For details see:
http://cvs.opensolaris.org/source/diff/on/usr/src/lib/libcfgadm/common/config_admin.c?r2=1.34&r1=1.33
The "Portions Copyright" clause is only necessary for contributions for which the contributor retains sole copyright ownership. For contributions under the terms of the Sun Contributor Agreement, the clause is unnecessary, because Sun is a joint copyright holder, and Sun's copyright notice suffices. All contributions being putback to the master Solaris source are required to be under the terms of the SCA, so the clauses in the aforementioned two examples are unnecessary, and Sun can (and should) remove them and also modify "Sponsor Tasks" to no longer allow vanity copyright notices to be added to code contributed under the SCA.
|
|
|
|
|
Posts:
3,835
From:
JP
Registered:
4/6/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 6, 2006 1:27 PM
in response to: gman
|
|
Glynn Foster wrote:
> So, from a development point of view, I was somewhat surprised, having
> never really looked at the ON code before, that there's no recognition
> of people who wrote the code in the source files.
Are we unusual in this respect? How do other open source communities do
it? Considering the size of our code base (and the age of some of it)
this could be challenging. :)
> Sure, there's probably
> some Teamware logs, but that doesn't feel as public as something like a
> ChangeLog [1] or author credits in the source code headers.
>
> As to how to recognize other contributions, that's generally a much
> harder thing to do - we're a community, and we're all in this together.
> Any one person is as important as the next one. While the occasional
> token of some free swag is a nice gesture for significant contributions,
> I don't think there needs to be a formal process. We just need to be
> better about praising each other on blogs/mailing lists/forums etc.
Yah, I don't want any kind of complex or formal process either, and I'd
like to stay way from any kind of rah-rah announcements. I'm just
looking to draw some well deserved attention to those who want it. I
want to give people the option, in other words.
> It's an amazing feeling getting a mail out of the blue saying 'Wow,
> thanks - that patch/contribution you did really rocked', and that is
> really one of the cornerstones of creating a fun, thriving open source
> community IMHO.
I agree. And I'd like to extend that feeling to those who don't code. As
we grow, more and more people will be contributing in more and more
ways. I'd like to outline some of those ways.
Jim
--
Jim Grisanzio, Community Manager, OpenSolaris
http://blogs.sun.com/jimgris/
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
476
From:
AU
Registered:
6/14/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 5, 2006 10:25 PM
in response to: jimgris
|
|
Look at what happens on java.net, key blogs of note are given prominence on the front page or what about something like developer spotlight like they are using on jxta.org?
That is an artificial way of doing things though, wouldn't you say that community recognition within a technocracy is more organic in nature?
|
|
|
|
|
Posts:
3,835
From:
JP
Registered:
4/6/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 6, 2006 9:33 AM
in response to: che
|
|
Ché Kristo wrote:
>
> Look at what happens on java.net, key blogs of note are given prominence on the front page or what about something like developer spotlight like they are using on jxta.org?
>
> That is an artificial way of doing things though, wouldn't you say that community recognition within a technocracy is more organic in nature?
>
This may not be popular among some, but I like java.net. From a content perspective, I mean. Individual community members come through more clearly on their site. Personally, I'd like to evolve to a model where we are constantly generating and editing more diverse content (blogs, articles, profiles, podcasts, surveys, awards, events, whatever) to reflect the diversity of the community (in the future). Generating content is a good way to draw attention to specific community members and their contributions, so thanks for pointing that out.
Is all this artificial? To some extent, sure, absolutely. But since we are creating something from nothing here we have to start somewhere, right? Also, I believe it's necessary if we want to keep engaging new people and growing the community. We have to give people a clear way to engage with OpenSolaris at multiple levels (that's the key), and recognizing people is just one way to do that. I don't want a heavyweight system, though, just to be clear. I'm just looking to cover the basics, the obvious things anyone would do to recognize someone else for a job well done.
I totally agree with your point about this being "organic" at some level, but I see that as addressing only a small percentage of the community -- those who are already familiar with the culture of communities and how credit is earned, etc. I blogged about this a while back: here:http://blogs.sun.com/roller/page/jimgris?entry=everyone_knows (so I'm still exploring it :)). I believe that part of the issue takes care of itself among those people. They all seem to know, I realize. But not everyone knows, and those are the guys I want to engage and offer some ways to get recognized if they want.
Jim
--
Jim Grisanzio, Community Manager, OpenSolaris
http://blogs.sun.com/jimgris/
|
|
|
|
|
Posts:
100
From:
ZA
Registered:
6/15/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 6, 2006 2:25 AM
in response to: jimgris
|
|
I would think a prominent <link> on the frontpage to an area called "OS Movers and Shakers" (or something) would be nice. The format can be anything, as long as people are recognized for their contributions.
Lots of customers here are watching the Open Solaris movement with interest, but are skeptical on the contribution made by people other than Sun employee's.
It would be nice to have a <http> to point them to as a testimony of regular folks ;) contributing.
|
|
|
|
|
Posts:
3,835
From:
JP
Registered:
4/6/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 6, 2006 8:34 AM
in response to: burgerw
|
|
Just as a starting point, we were going to re-work these pages:
http://opensolaris.org/os/bug_reports/
http://opensolaris.org/os/bug_reports/request_sponsor/
to reflect more general contributions (both code and non-code). Basically make them both into a "contributor" page/section to include names, the specific contributions, testimonials, photos, awards, whatever (just brainstorming here). That request-sponsor code page is already linked off the front page. Also, I'd like to update
http://opensolaris.org/os/communities/participation/ to point to the new "contributor" page. At the very least, we should be able to clean some of this up and make the info easier to find.
Regarding the customers ... I agree. We heard that a lot during the pre-pilot phase. Almost all the customers I spoke with said that they loved the idea of opening Solaris but that a requirement would be to keep our development processes (updated and opened, of course). So, I think we were in line from way back.
Jim
--
Jim Grisanzio, Community Manager, OpenSolaris
http://blogs.sun.com/jimgris/
|
|
|
|
|
Christopher Mahan
chris_mahan@yahoo.com
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 6, 2006 7:32 PM
in response to: jimgris
|
|
Jim, how about giving them a @opensolaris.org email address? I know
some people that treasure their @apache.org addy.
The other thing is that you want to remember to keep the rules to an
absolute minimum. You want the Very Best hackers out there to work on
the code. These people are traditionally staunch non-conformists and
generally dislike doing anything they see as pointless. For example:
if you had a rule that said: "no email address in the code" then the
hacker will think: "They had to make a rule for that? Silly people."
Instead, encourage very strong collaboration.
For the non-coders, their name and email, and/or web address on the
documents they work on. For example, if there is a web page on the
sun website, have a contact. See http://www.w3.org/MarkUp/, at the
bottom, in contact. The guy's name links to
http://www.w3.org/People/mimasa/, a page which has his email, and
which he quite obviously authored himself.
Now, the w3 is not some fly-by-night group. Note the guy's email
addy: "mimasa at w3 dot org" That's gotta have street cred. And the fact
that his name appears on one of the principal pages for the HTML
standard body for the Entire World has got to have some street cred
too.
Also, in communications, use their full name. It really helps down
the road when connecting the dots. If you say Matt worked on this
function, it's not quite as effective as saying "Matthew Yardley
wrote a function, it was great, Thanks Matt!!!"
It just seems a little bit more formal, a little bit more respectful,
a bit less familiar, but I think in that sense formal is good too.
Chris Mahan
818.943.1850 cell
chris_mahan at yahoo dot com
chris dot mahan at gmail dot com
http://www.christophermahan.com/
__________________________________________
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
3,835
From:
JP
Registered:
4/6/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 9, 2006 2:03 PM
in response to: Christopher Mahan
|
|
Christopher Mahan wrote:
> Jim, how about giving them a @opensolaris.org email address? I know
> some people that treasure their @apache.org addy.
Humm. This is interesting. I seem to remember this coming up with the
early governance discussions (either in the pilot or afterwards). I'll
check.
> The other thing is that you want to remember to keep the rules to an
> absolute minimum.
Totally agree.
> You want the Very Best hackers out there to work on
> the code. These people are traditionally staunch non-conformists and
> generally dislike doing anything they see as pointless.
I'm learning this, yes. :)
> For example:
> if you had a rule that said: "no email address in the code" then the
> hacker will think: "They had to make a rule for that? Silly people."
>
> Instead, encourage very strong collaboration.
>
>
> For the non-coders, their name and email, and/or web address on the
> documents they work on. For example, if there is a web page on the
> sun website, have a contact. See http://www.w3.org/MarkUp/, at the
> bottom, in contact. The guy's name links to
> http://www.w3.org/People/mimasa/, a page which has his email, and
> which he quite obviously authored himself.
I like this. We have community leaders visible, but it's not easy to see
who writes what on the pages.
> Now, the w3 is not some fly-by-night group. Note the guy's email
> addy: "mimasa at w3 dot org" That's gotta have street cred. And the fact
> that his name appears on one of the principal pages for the HTML
> standard body for the Entire World has got to have some street cred
> too.
>
> Also, in communications, use their full name. It really helps down
> the road when connecting the dots. If you say Matt worked on this
> function, it's not quite as effective as saying "Matthew Yardley
> wrote a function, it was great, Thanks Matt!!!"
> It just seems a little bit more formal, a little bit more respectful,
> a bit less familiar, but I think in that sense formal is good too.
>
>
> Chris Mahan
> 818.943.1850 cell
> chris_mahan at yahoo dot com
> chris dot mahan at gmail dot com
> http://www.christophermahan.com/
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
364
From:
US
Registered:
7/28/05
|
|
|
|
Re: Ideas for Recognition to Build Reputation
Posted:
Jan 9, 2006 10:54 AM
in response to: jimgris
|
|
> We are 7 months into the project now, we are entering a new year, and I think it's time
> start recognizing community members who are contributing and participating in
> OpenSolaris.
I was curious about this topic for some time, and one of the most favored ways for recognition seems to be to have the names of contributors on the OS.o website. If we can have www.opensolaris.org/contributors.html or something along this line (recognition.html ?), this gives the contributors something to show for. An easy and straightforward URL would be a big plus.
Young
|
|
|
|
|
Posts:
3,835
From:
JP
Registered:
4/6/05
|
|
|
|
Re: Re: Ideas for Recognition to Build Reputation
Posted:
Jan 9, 2006 1:44 PM
in response to: yjsong
|
|
Young Joo Song wrote:
>>We are 7 months into the project now, we are entering a new year, and I think it's time
>>start recognizing community members who are contributing and participating in
>>OpenSolaris.
>
>
> I was curious about this topic for some time, and one of the most favored ways for recognition seems to be to have the names of contributors on the OS.o website. If we can have www.opensolaris.org/contributors.html or something along this line (recognition.html ?), this gives the contributors something to show for. An easy and straightforward URL would be a big plus.
Thanks, Young. I agree (as do many others). We're working it.
Jim
--
Jim Grisanzio, Community Manager, OpenSolaris
http://blogs.sun.com/jimgris/
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
