Discussion - more information on project pages

Hi all. I'd like to get feed back on adding additional information to the
project pages. Specifically I'd like to add:

* SPI services that the project is actively using and any that it has
declined to use (some projects have declined to accept donations via SPI).

* The name of the current project liaison (but not any contact details,
for privacy).

* How the project liaison is selected/elected, with links where relevant.

* Anything unusual or notable about the arrangement with SPI (eg, for
OpenVAS, 2 of 3 designated decision makers must agree before they speak as
the project liaison).

This would have a number of advantages:

* It would be a useful reference for SPI board and committee members when
dealing with projects.

* It would be a useful reference for project members in understanding what
services SPI is delivering to them and who their liaison is.

The alternative would be to put a second page for each project with these
details but I'd prefer to put it all on the one page.

Cheers,

Rob

--
Email: robert(at)spi-inc(dot)org Linux counter ID #16440
IRC: Solver (OFTC & Freenode)
Web: http://www.spi-inc.org
Director, Software in the Public Interest (http://spi-inc.org/)
Open Source: The revolution that silently changed the world

Robert Brockway <robert(at)spi-inc(dot)org> wrote:

> Hi all. I'd like to get feed back on adding additional information to
> the project pages. Specifically I'd like to add:
>
> * SPI services that the project is actively using and any that it has
> declined to use (some projects have declined to accept donations via
> SPI).

I think a complete list of services SPI is currently providing
and instructions how a project can apply for them would be useful,
too.

Maybe something like this is already available and I'm
just not aware of it?

> * The name of the current project liaison (but not any contact details,
> for privacy).

Are there any liaisons whose email address isn't publicly
available on the associated project's website (or the net
in general) anyway?

> * How the project liaison is selected/elected, with links where relevant.
>
> * Anything unusual or notable about the arrangement with SPI (eg, for
> OpenVAS, 2 of 3 designated decision makers must agree before they speak
> as the project liaison).
>
> This would have a number of advantages:
>
> * It would be a useful reference for SPI board and committee members
> when dealing with projects.
>
> * It would be a useful reference for project members in understanding
> what services SPI is delivering to them and who their liaison is.

Agreed.

Fabian

On Mon, 12 Sep 2011, Fabian Keil wrote:

> I think a complete list of services SPI is currently providing
> and instructions how a project can apply for them would be useful,
> too.

Hi Fabian. I've proposed a new version of the Associated Project Howto in
another thread (http://www.spi-inc.org/drafts/associated-project-howto/)
that includes a list of services that SPI offers.

>> * The name of the current project liaison (but not any contact details,
>> for privacy).
>
> Are there any liaisons whose email address isn't publicly
> available on the associated project's website (or the net
> in general) anyway?

True it would be fine to list their email addresses (personal or generic
for the role). Other contact details that we have would not be displayed
publically.

Cheers,

Rob

--
Email: robert(at)spi-inc(dot)org Linux counter ID #16440
IRC: Solver (OFTC & Freenode)
Web: http://www.spi-inc.org
Director, Software in the Public Interest (http://spi-inc.org/)
Open Source: The revolution that silently changed the world

Robert Brockway <robert(at)spi-inc(dot)org> wrote:

> On Mon, 12 Sep 2011, Fabian Keil wrote:
>
> > I think a complete list of services SPI is currently providing
> > and instructions how a project can apply for them would be useful,
> > too.
>
> Hi Fabian. I've proposed a new version of the Associated Project Howto
> in another thread
> (http://www.spi-inc.org/drafts/associated-project-howto/) that includes
> a list of services that SPI offers.

I'm aware of that, but I always thought the list wasn't complete. Is it?

It also doesn't mention how a project applies for the services
(with a few exceptions) and the rules don't seem to be too clear
to me.

For example I'm currently trying to figure out how to best pay
the fees for a project domain with the funds SPI holds for the
project (Privoxy).

The options seem to be:

1) A project member owns the domain, pays the fees and gets
reimbursed by the treasurer. The process is documented
as far as SPI is concerned (talk to the treasurer),
but the domain owner becomes a single point of failure.

2) Like #1, but if the associated project is a legal entity
it could own the domain itself. Unfortunately that's not
the case for Privoxy.

3) The domain is transferred to SPI. The process doesn't seem
to be documented at all and I assume the domain counts as an
asset which may never be transferred back, or to another non-US
non-profit. It's also not clear what the costs would be or what
happens if the project's funds are suddenly diminished.

4) Maybe a "Signing Contracts" solution is possible without
the domain being transferred to SPI, but I'm not too sure
about this.

5) Maybe the domain could be transferred to one of the European
partner organization, but that's a wild guess.

While it seems like an issue many associated projects (or projects
considering to become one) would have, there doesn't seem to be
any documentation except for the rather vague list of services.

Therefore I think it would be useful to establish which services
are the most common ones, to document what a project has to do
to get them and what the rules and consequences are.

Fabian

Fabian Keil writes ("Re: Discussion - more information on project pages"):
> 3) The domain is transferred to SPI. The process doesn't seem
> to be documented at all and I assume the domain counts as an
> asset which may never be transferred back, or to another non-US
> non-profit. It's also not clear what the costs would be or what
> happens if the project's funds are suddenly diminished.

We should see if we can get some advice on what SPI might be able to
do if a project wanted to disassociate with SPI and have the domain
name transferred to a new entity which might not be in the US or might
not be a formally set up charity. But even if the registration has to
stay with SPI, we could point the domain to the project's nameservers
in the usual way.

But aside from that question, I think this is a good option. It's not
expensive since domain registrations aren't, generally.

Ian.

On Mon, 19 Sep 2011, Fabian Keil wrote:

>> (http://www.spi-inc.org/drafts/associated-project-howto/) that includes
>> a list of services that SPI offers.
>
> I'm aware of that, but I always thought the list wasn't complete. Is it?

I think I covered the major services. Part of the reason I want feedback
is to make sure I didn't miss anything significant.

> It also doesn't mention how a project applies for the services
> (with a few exceptions) and the rules don't seem to be too clear
> to me.

I understand this would generally occur through the liaison requesting
that the board make a particular service available to the project. The
liaison and the board could then discuss the particulars and move forward
if there was agreement.

> For example I'm currently trying to figure out how to best pay
> the fees for a project domain with the funds SPI holds for the
> project (Privoxy).
>
> The options seem to be:
>
> 3) The domain is transferred to SPI. The process doesn't seem
> to be documented at all and I assume the domain counts as an
> asset which may never be transferred back, or to another non-US

This is an option that a number of associated projects use.

You raise an interesting question concerning transfer of domain names
after acceptance by a US 501(c)(3). I personally can't answer that
question.

> non-profit. It's also not clear what the costs would be or what
> happens if the project's funds are suddenly diminished.

An actively used domain name is a valuable asset and it's loss would be
very damaging to an active project. I would fully support SPI renewing an
actively used domain name in an emergency even if project funds did not
cover the cost at that time.

Having said that, some (all?) registrars allow a domain to be renewed by a
3rd party so I don't believe any active project would be at risk of its
domain name expiring.

> While it seems like an issue many associated projects (or projects
> considering to become one) would have, there doesn't seem to be
> any documentation except for the rather vague list of services.
>
> Therefore I think it would be useful to establish which services
> are the most common ones, to document what a project has to do
> to get them and what the rules and consequences are.

I'd be happy to do a page like this.

Cheers,

Rob

--
Email: robert(at)spi-inc(dot)org Linux counter ID #16440
IRC: Solver (OFTC & Freenode)
Web: http://www.spi-inc.org
Director, Software in the Public Interest (http://spi-inc.org/)
Open Source: The revolution that silently changed the world