Today I received a check from InfraDNA for the last remaining 1/3 ownership of
cucumber (the first community owned machine) so I wanted to raise the subject
of stewardship since we've been operating largely on our own volition thus far.
Here's some proposals, currently only pertaining to cucumber for now, until we
purchase more hardware. ("infra" hereafter referring to InfraDNA, abayer and
myself)
Machine Access: Since the machine(s) are not realistically needed for
contributing to the project in any significant manner, I propose a required
unanimous approval from infra for new shell accounts on the machine
Services Access: All services (Hudson, Drupal, etc) operated on the
machine shall remain open to
Hudson community members and contributors. Access will be opt-in rather than
opt-out and not require infra approval but rather notification. Access to
portions of services that have security implications, spinning up EC2
instances, compiling code, adding projects, etc should however require approval.
Content: All content created via these community services should remain open
to the greater Hudson community. Content should be licensed under the CC 3.0
Attribution license [1]
The question of sponsorship is a tricky one, and I'm not sure if I have any
reasonable proposals as of yet for how we can handle that. For example, if
InfraDNA, Oracle, or any other company sponsor this year's hosting costs of
cucumber, what does that imply said sponsor is entitled to with regards to
community involvement/direction, stewardship of resources, etc. This will
likely invoke a discussion of a "Hudson Labs Foundation" which I don't feel
like getting into on this thread. As for now, sponsorship will simply mean a
logo and a link as far as I'm concerned.
I'm curious what you guys think of this? I've not been in this position before,
but I want to make some things clear ahead of time before we find ourselves
quarreling over who gets access to what, etc.
[1] http://creativecommons.org/licenses/by/3.0/
Cheers,
-R. Tyler Ballance
--------------------------------------
Jabber: rtyler@jabber.org
GitHub: http://github.com/rtyler
Identica: http://identi.ca/dero
Twitter: http://twitter.com/agentdero
Blog: http://unethicalblogger.com
Sounds reasonable to me. Given where I am now, I have some interest and bias on the point of sponsorship, so I'll probably end up bringing that up down the road. On 06/05/2010 07:27 PM, R. Tyler Ballance wrote: > Today I received a check from InfraDNA for the last remaining 1/3 ownership of > cucumber (the first community owned machine) so I wanted to raise the subject > of stewardship since we've been operating largely on our own volition thus far. > > Here's some proposals, currently only pertaining to cucumber for now, until we > purchase more hardware. ("infra" hereafter referring to InfraDNA, abayer and > myself) > > > Machine Access: Since the machine(s) are not realistically needed for > contributing to the project in any significant manner, I propose a required > unanimous approval from infra for new shell accounts on the machine > > > Services Access: All services (Hudson, Drupal, etc) operated on the machine shall remain open to > Hudson community members and contributors. Access will be opt-in rather than > opt-out and not require infra approval but rather notification. Access to > portions of services that have security implications, spinning up EC2 > instances, compiling code, adding projects, etc should however require approval. > > > Content: All content created via these community services should remain open > to the greater Hudson community. Content should be licensed under the CC 3.0 > Attribution license [1] > > > The question of sponsorship is a tricky one, and I'm not sure if I have any > reasonable proposals as of yet for how we can handle that. For example, if > InfraDNA, Oracle, or any other company sponsor this year's hosting costs of > cucumber, what does that imply said sponsor is entitled to with regards to > community involvement/direction, stewardship of resources, etc. This will > likely invoke a discussion of a "Hudson Labs Foundation" which I don't feel > like getting into on this thread. As for now, sponsorship will simply mean a > logo and a link as far as I'm concerned. > > > I'm curious what you guys think of this? I've not been in this position before, > but I want to make some things clear ahead of time before we find ourselves > quarreling over who gets access to what, etc. > > > > > [1] http://creativecommons.org/licenses/by/3.0/ > > Cheers, > -R. Tyler Ballance > -------------------------------------- > Jabber: rtyler@jabber.org > GitHub: http://github.com/rtyler > Identica: http://identi.ca/dero > Twitter: http://twitter.com/agentdero > Blog: http://unethicalblogger.com > -- Kohsuke Kawaguchi | InfraDNA, Inc. | http://infradna.com/
all sounds fine to me.
logo+link for sponsorship seems a good standard; if they want something
more, that would be a special discussion, and perhaps could generally be
steered towards a project with InfraDNA rather than a sponsorship deal.
- Alan
R. Tyler Ballance wrote:
> Today I received a check from InfraDNA for the last remaining 1/3 ownership of
> cucumber (the first community owned machine) so I wanted to raise the subject
> of stewardship since we've been operating largely on our own volition thus far.
>
> Here's some proposals, currently only pertaining to cucumber for now, until we
> purchase more hardware. ("infra" hereafter referring to InfraDNA, abayer and
> myself)
>
>
> Machine Access: Since the machine(s) are not realistically needed for
> contributing to the project in any significant manner, I propose a required
> unanimous approval from infra for new shell accounts on the machine
>
>
> Services Access: All services (Hudson, Drupal, etc) operated on the
machine shall remain open to
> Hudson community members and contributors. Access will be opt-in rather than
> opt-out and not require infra approval but rather notification. Access to
> portions of services that have security implications, spinning up EC2
> instances, compiling code, adding projects, etc should however require approval.
>
>
> Content: All content created via these community services should remain open
> to the greater Hudson community. Content should be licensed under the CC 3.0
> Attribution license [1]
>
>
> The question of sponsorship is a tricky one, and I'm not sure if I have any
> reasonable proposals as of yet for how we can handle that. For example, if
> InfraDNA, Oracle, or any other company sponsor this year's hosting costs of
> cucumber, what does that imply said sponsor is entitled to with regards to
> community involvement/direction, stewardship of resources, etc. This will
> likely invoke a discussion of a "Hudson Labs Foundation" which I don't feel
> like getting into on this thread. As for now, sponsorship will simply mean a
> logo and a link as far as I'm concerned.
>
>
> I'm curious what you guys think of this? I've not been in this position before,
> but I want to make some things clear ahead of time before we find ourselves
> quarreling over who gets access to what, etc.
>
>
>
>
> [1] http://creativecommons.org/licenses/by/3.0/
>
> Cheers,
> -R. Tyler Ballance
> --------------------------------------
> Jabber: rtyler@jabber.org
> GitHub: http://github.com/rtyler
> Identica: http://identi.ca/dero
> Twitter: http://twitter.com/agentdero
> Blog: http://unethicalblogger.com
>
>
All sounds reasonable to me. A. On Mon, Jun 7, 2010 at 10:51 AM, Alan Harder <mindless@dev.java.net> wrote: > all sounds fine to me. > logo+link for sponsorship seems a good standard; if they want something > more, that would be a special discussion, and perhaps could generally be > steered towards a project with InfraDNA rather than a sponsorship deal. > > - Alan > > > R. Tyler Ballance wrote: > > Today I received a check from InfraDNA for the last remaining 1/3 > ownership of > > cucumber (the first community owned machine) so I wanted to raise the > subject > > of stewardship since we've been operating largely on our own volition > thus far. > > > > Here's some proposals, currently only pertaining to cucumber for now, > until we > > purchase more hardware. ("infra" hereafter referring to InfraDNA, abayer > and > > myself) > > > > > > Machine Access: Since the machine(s) are not realistically needed for > > contributing to the project in any significant manner, I propose a > required > > unanimous approval from infra for new shell accounts on the machine > > > > > > Services Access: All services (Hudson, Drupal, etc) operated on the > machine shall remain open to > > Hudson community members and contributors. Access will be opt-in rather > than > > opt-out and not require infra approval but rather notification. Access to > > portions of services that have security implications, spinning up EC2 > > instances, compiling code, adding projects, etc should however require > approval. > > > > > > Content: All content created via these community services should remain > open > > to the greater Hudson community. Content should be licensed under the CC > 3.0 > > Attribution license [1] > > > > > > The question of sponsorship is a tricky one, and I'm not sure if I have > any > > reasonable proposals as of yet for how we can handle that. For example, > if > > InfraDNA, Oracle, or any other company sponsor this year's hosting costs > of > > cucumber, what does that imply said sponsor is entitled to with regards > to > > community involvement/direction, stewardship of resources, etc. This will > > likely invoke a discussion of a "Hudson Labs Foundation" which I don't > feel > > like getting into on this thread. As for now, sponsorship will simply > mean a > > logo and a link as far as I'm concerned. > > > > > > I'm curious what you guys think of this? I've not been in this position > before, > > but I want to make some things clear ahead of time before we find > ourselves > > quarreling over who gets access to what, etc. > > > > > > > > > > [1] http://creativecommons.org/licenses/by/3.0/ > > > > Cheers, > > -R. Tyler Ballance > > -------------------------------------- > > Jabber: rtyler@jabber.org > > GitHub: http://github.com/rtyler > > Identica: http://identi.ca/dero > > Twitter: http://twitter.com/agentdero > > Blog: http://unethicalblogger.com > > > > >