CreateJS Community Mission #4
Conversation
| @@ -0,0 +1,51 @@ | |||
| # CreateJS Consortium | |||
There was a problem hiding this comment.
This isn't in the proper format - content needs to be moved into the file below.
| ## Research | ||
|
|
||
| https://producingoss.com | ||
| https://guides.github.com |
There was a problem hiding this comment.
There's quite a few things in these to consider. I think everyone interested in becoming a core member should have a read.
There was a problem hiding this comment.
We can draw out important aspects, and codify them in this RFC.
| - RFC PR: (after opening the RFC PR, update this with a link to it and update the file name) | ||
| - Relevant Project: (e.g. EaselJS, SoundJS, PreloadJS, TweenJS, ...) | ||
|
|
||
| # CreateJS Consortium |
There was a problem hiding this comment.
Is consortium even the right name? I'm happy to run with it for now, but I'm not certain we'd need to refer to it this way once decided how we do stuff.
There was a problem hiding this comment.
Here is Webster's definition:
Consortium: an agreement, combination, or group (as of companies) formed to undertake an enterprise beyond the resources of any one member. E.g. A consortium of researchers decoded the honeybee genome.
Sounds friendly in that example... but usually it sounds business-like and might get confused with a Cartel, etc. Anyway - it has alliteration CreateJS Consortium. Its definition fits. It sounds official and it holds weight. But... is it cool? Is it nerdy enough? It is not as fun as CreateJS Crew... etc. Maybe all the consortium does is put together the plan and that includes a name for the future!
There was a problem hiding this comment.
Not that I'm that bothered by it, just giving my 2c: I've not heard 'Consortium' used on open source projects. Off the top of my head, there's usually a community, and some kind of core leadership. In my opinion is that there's great benefit in helping the community getting involved. This means removing barriers to contribution from a range of expertise levels. This might mean defining what can be done, how to do it, and how it will be lead/managed/guided/moderated etc by the core team.
Is the core team the consortium?
Anyway - again, I'm not too fussed by naming.
Consortium.md
Outdated
| @@ -0,0 +1,51 @@ | |||
| # CreateJS Consortium | |||
|
|
|||
| The GSkinner team is handing the CreateJS project over to the community. | |||
There was a problem hiding this comment.
Perhaps: "The GSkinner team is encouraging the community to get involved in in the maintenance and direction of CreateJS."
I am not sure they are ready to give it up completely. Probably a side-by-side approach may be the way to look at it. So the title - "Start a consortium to take over CreateJS" may be a bit dramatic - although it does sound like what consortia do! How about "Inititial Proposal to help maintain CreateJS".
From a meta standpoint... can we edit this document directly anywhere? Or do we just provide comments? Also... what is the "Start a review" button and when would we use it?
There was a problem hiding this comment.
Good point. I had made some assumptions about what was happening. Happy to reword.
To edit, you can certainly submit a PR to merge into my PR branch on my jedateach github. I might somehow be able to give you permission to edit my branch directly from this ui.
There was a problem hiding this comment.
@jedateach - change of mind a little on the title. We have some questions to ask Grant to better help us with a mission document. Let's ask those questions just on Slack. And so this document becomes the mission document. So we could title it: "CreateJS Community Mission". And perhaps we can refer to ourselves as the CreateJS Community? Or is that too generic. It also has alliteration and is maybe more friendly sounding.
jedateach
changed the title
This is really draft at the moment, but thought I'd throw up the current state to see if anyone wants to throw in any thoughts.
The idea is to make and document some foundational decisions.
There is also discussion happening over on Slack, which could be incorporated here.