Giving Webmachine its own GitHub Organization #58
Comments
|
Discussing a little more, it seems a README-only wouldn't work given we'll want to build from it. The Basho org will need to fork Webmachine and whoever acts as shepherd will update from origin. I think a custom README is important as well to explain the move. Maybe it will make sense to update the main README anyway and that will cover the conversation. |
|
@mjbrender In anticipation of this move, @joedevivo established the wrq organization (and we forked webmachine there later). You could use that organization, or create another. My main concerns are:
|
|
I am for this move and the community involvement will drive the priority. |
|
If engineering resources are the concern, would it be better for Basho to Jordan On Fri, May 29, 2015 at 8:46 AM, HMcKelvey notifications@github.com wrote:
|
|
@jrwest Exactly, there is precedent here. |
|
Jordan and Sean, On Fri, May 29, 2015 at 9:15 AM, Sean Cribbs notifications@github.com
Heather McKelvey |
|
Great :). If Basho does not feel they can provide the resources I am happy On Fri, May 29, 2015 at 9:21 AM, HMcKelvey notifications@github.com wrote:
|
|
Also, while we are going through this exercise could we also discuss moving On Fri, May 29, 2015 at 9:29 AM, Jordan West jordanrw@gmail.com wrote:
|
|
One step at a time @jrwest - please open another Issue in this repo to discuss doing so. Let's focus on Webmachine right now to start. @seancribbs the main concerns you outlined are identical to our own. I have the utmost trust you'll help us responsibly pass ownership to a 3rd party. The direction of Webmachine would be based on its core maintainers, some of who may be Basho engineers and some not. It's not about their affiliation with a company - it's about their dedication to the community process. We don't have to go full Apache process on this, but some structure is nice. @jrwest, I don't anticipate we can safely by the end of the weekend, but we can and will certainly start the process. I'll keep in touch on timing. @seancribbs, your domain knowledge in who and what to assure we don't break (too many) things in the process would be lovely. |
|
Happy to open a separate issue if that is the way you would prefer it done As for my offer to do the work, I only mentioned as early as this weekend On Fri, May 29, 2015 at 10:42 AM, Matt Brender notifications@github.com
|
|
@jrwest sounds good. I'm happy to have your expertise here. Great news - the user on @webmachine has given up the handle for us. I made an organization and will start working on team membership when I get free time this afternoon. @seancribbs, I plan to make you owner and bow out of the org given that I know 0 about Webmachine 😄. It's all you. Woot, progress! |
|
@mjbrender Excellent! |
|
Hey @seancribbs - I've begun to update the organization. I haven't made headway on ensuring migration won't break all the things internally. Let me know if you're aware of internal gotchas that I wouldn't be. |
|
@mjbrender Immediately after the transfer, you should likely fork back to the "basho" organization to prevent breakages. Aside from putting the appropriate people in the "Owners" team, I can't think of what else needs doing. |
|
Hi Matt,I just have one concern about the name webmachine. I have used it for years in accounts I have on the web - forums, software sites etc - probably much longer than your use on GitHub.. You would not come back sometime in the future and tell me I can't use that name any more there because you have some sort of trademark on it, would you?JeanJean BraithwaiteWeb Design & Development(416) 993-7323http://jaybeeweb.com -------- Original Message -------- Hey @seancribbs - I've begun to update the organization. I haven't made headway on ensuring migration won't break all the things internally. Let me know if you're aware of internal gotchas that I wouldn't be. —Reply to this email directly or view it on GitHub. |
|
@jaybeeweb The "webmachine" project existed long before Github, at least back to 2009, if not earlier. Here is the first commit imported into Bitbucket by @justinsheehy: https://bitbucket.org/justin/webmachine/commits/e68ae3bcc0908e5d9e26c99dd058c00bb4ca0298 It was imported to Github some years later when Basho made the switch to git. |
|
For the record: the first publicly visible commits to webmachine were on Google Code in March 2008. Also, trademarks do not cover use of a name in general but rather the use of that name to describe specific goods or services and to distinguish them from similar goods or services provided by another party. I wouldn't be that concerned on this count unless you are making software similar to webmachine. |
|
I've been using this username on my accounts since before 2007 (case in point Sitepoint forums) - I just want assurance that I will not be asked to totally abandon it.Jean BraithwaiteWeb Design & Development(416) 993-7323http://jaybeeweb.com -------- Original Message -------- @jaybeeweb The "webmachine" project existed long before Github, at least back to 2009, if not earlier. Here is the first commit imported into Bitbucket by @justinsheehy: https://bitbucket.org/justin/webmachine/commits/e68ae3bcc0908e5d9e26c99dd058c00bb4ca0298 It was imported to Github some years later when Basho made the switch to git. —Reply to this email directly or view it on GitHub. |
|
Thank you.Jean BraithwaiteWeb Design & Development(416) 993-7323http://jaybeeweb.com -------- Original Message -------- For the record: the first publicly visible commits to webmachine were on Google Code in March 2008. Also, trademarks do not cover use of a name in general but rather the use of that name to describe specific goods or services and to distinguish them from similar goods or services provided by another party. I wouldn't be that concerned on this count unless you are making software similar to webmachine. —Reply to this email directly or view it on GitHub. |
|
Hey @jaybeeweb - I can assure you that we do not intent to ask you to abandon the name. Your willingness to pass it over on GitHub was kind of you and I have no further expectations on its use. I'm no lawyer and have nothing reassuring to add beyond this point. Thanks again for your kindness - there's no reason for proof of lineage. |
|
Hey @seancribbs - I'm connecting with @jonmeredith tomorrow. You both have been added to the organization as owners and @jrwest is in there as a maintainer. I'm talk through details w/Jon and migrate the main repo over tomorrow if all goes well. From there, Sound good? |
will be enabled and I'm trusting you'll shepherd in a healthy group of maintainers that can bring the project forward.
|
I want to give a big +1 to this - although webmachine is a core component of Riak CS, Basho haven't invested much time on webmachine. I also want to see good different quip in every release. |
|
@mjbrender We will nurture it well. |
|
I think this is an excellent idea. A big +1. This will get me motivated to go fix this issue (mochi/mochiweb#146) as well. |
|
@mjbrender Any progress on transferring the repository? |
|
@seancribbs planning for EOD today. cc @HMcKelvey @jonmeredith |
|
I'm glad to see this come to conclusion. Thanks again for your help leading us through it @seancribbs and @jonmeredith. |
I'm working on the logistics to get the Webmachine project its own organization. It would benefit our greater community by passing responsibility of a well-adopted project to a larger organization of people, however informal, to curate.
Let's discuss how to achieve this.
One minor blocker is the fact @webmachine is not available for an Organization due to the existence of a user by that name. I've reached out in this GitHub issue to see if s/he would be kind enough to pass us that name. Either way, this preferred handle should no prevent us from thinking through next steps.
Initial thoughts:
Some concerns:
With that, let's get this discussion going.
The text was updated successfully, but these errors were encountered: