welcome: please sign in

Diff for "RobinTempleton"

Differences between revisions 1 and 45 (spanning 44 versions)
Revision 1 as of 2011-02-23 01:40:58
Size: 932
Comment: new page
Revision 45 as of 2015-04-15 04:59:38
Size: 3671
Comment: rm registered agent todo (no longer requires silverlight)
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== 2010 Board Statement == ## page was renamed from BtTempleton
#pragma section-numbers off
Line 3: Line 4:
I have been a member of HCoop since 2005; I wrote the Domtool Emacs mode, was involved in the 2009 migration project, started the hcoopstatus Identica group, and am redesigning the member portal. My platform: HCoop user bpt; member since 2005, Secretary 2011--present
Line 5: Line 6:
 * Plan to expand to 150--250 members during the next year and then end the pledge system once we can do so without increasing dues significantly. == Board statement 2015 ==
Line 7: Line 8:
 * Move HCoop accounts to the National Cooperative Bank or a similar credit union. I have been a member of HCoop since 2005 and currently serve as Secretary; I also run [[http://planet.hcoop.net/|Planet HCoop]] and have contributed to Domtool. My platform:
Line 9: Line 10:
 * Implement a strong environmental policy when we are financially able to; purchase carbon offsets to compensate for our use of nonrenewable energy.  1. Purchase and install a new server as soon as possible so that we can responsibly expand our membership.
 1. Expand membership through word-of-mouth recommendations and grassroots campaigns.
 1. Recruit system administration volunteers so that we can provide new services, like microblogging and Media''''''Goblin.
 1. Adopt a license policy to make our future software and documentation free (documentation is currently non-free).
 1. Adopt an EnvironmentalPolicy requiring that we offset the pollution we generate.
 1. Move our accounts to the National Cooperative Bank or a credit union.
Line 11: Line 17:
 * Document development processes for our custom software and recruit a fourth admin. Also consider making it possible for admins to delegate certain tasks to trusted non-admins. == OpenID server ==
Line 13: Line 19:
 * Last but not least, I will have HCoop T-shirts printed, finishing the project that NathanKennedy began in 2005. (: Would it make sense for HCoop to be an [[http://openid.net/|OpenID]] provider? [[http://pypi.python.org/pypi/gracie/0.2.6|Gracie]] is a server that authenticates users using PAM, and it's in Debian. We could allow users to register their identity URIs using domtool, as well as supporting `http://hcoop.net/~user` automatically.

== *scratch* ==

Gitweb URIs: Repo.or.cz uses cleaner URIs than gitweb's defaults -- for example, `/w/foo.git/commit/abcdef` for viewing an individual commit. We should patch our gitweb script to provide something similar.

Provide more VCS web interfaces: eventually we should have some subset of darcshub, darcsweb, hgweb, gitorious, cgit, extended gitweb, maybe even Sourceforge or Savane

Fix moinmoin headings somehow. Many pages use H1 for section titles which makes the outline (in the html5 sense) nonsensical and contradicts w3c recommendations

Fix defaults that lead to serving the same resource from multiple URIs. In particular, don't serve files from `public_html` from domains by default, and use permanent redirects from the `www` subdomain to the bare domain name or vice versa

Poll members about what they would like to do with free social networking services (e.g., ostatus, mediagoblin); what approaches they would prefer for vanity domains vs. central installations; use by non-members (e.g. will their friends want to use their installations, would their friends join hcoop, etc.); semi-managed installations vs. manual individual administration; ...

Implement portal redesign: http://hcoop.net/~bpt/tmp/portal.html

Find out whether we can accept copyright assignments

Pass [[https://lists.hcoop.net/pipermail/hcoop-misc/2008-February/000082.html|ntk's anti-FISA policy]]

Moniker TODOs: Keep changes in version control. Reduce wasted white space at top of page. Center HCoop logo.

Policy/guideline ideas:

Licensing policy: (A)GPLv3-compatible for software, the usual free content licenses for other things? We may want an exception for logos, or just protect them as trademarks like Debian does. The content license(s) should ideally be GPL-compatible since we probably have some "content" that is GPL (like domtool docstrings). Relicensing the wiki may be difficult, but there are probably not many (15, 20?) contributors of substantial amounts of currently-relevant text, excluding homepages.

Internal writing guidelines: use gender-inclusive language; promote only FreeSoftware officially, and ask that people consider FreeSoftware principles and the SevenPrinciples when officially recommending a service or organization; write "GNU/Linux" instead of "Linux" when referring to the entire OS

----
CategoryHomepage

HCoop user bpt; member since 2005, Secretary 2011--present

Board statement 2015

I have been a member of HCoop since 2005 and currently serve as Secretary; I also run Planet HCoop and have contributed to Domtool. My platform:

  1. Purchase and install a new server as soon as possible so that we can responsibly expand our membership.
  2. Expand membership through word-of-mouth recommendations and grassroots campaigns.
  3. Recruit system administration volunteers so that we can provide new services, like microblogging and MediaGoblin.

  4. Adopt a license policy to make our future software and documentation free (documentation is currently non-free).
  5. Adopt an EnvironmentalPolicy requiring that we offset the pollution we generate.

  6. Move our accounts to the National Cooperative Bank or a credit union.

OpenID server

Would it make sense for HCoop to be an OpenID provider? Gracie is a server that authenticates users using PAM, and it's in Debian. We could allow users to register their identity URIs using domtool, as well as supporting http://hcoop.net/~user automatically.

*scratch*

Gitweb URIs: Repo.or.cz uses cleaner URIs than gitweb's defaults -- for example, /w/foo.git/commit/abcdef for viewing an individual commit. We should patch our gitweb script to provide something similar.

Provide more VCS web interfaces: eventually we should have some subset of darcshub, darcsweb, hgweb, gitorious, cgit, extended gitweb, maybe even Sourceforge or Savane

Fix moinmoin headings somehow. Many pages use H1 for section titles which makes the outline (in the html5 sense) nonsensical and contradicts w3c recommendations

Fix defaults that lead to serving the same resource from multiple URIs. In particular, don't serve files from public_html from domains by default, and use permanent redirects from the www subdomain to the bare domain name or vice versa

Poll members about what they would like to do with free social networking services (e.g., ostatus, mediagoblin); what approaches they would prefer for vanity domains vs. central installations; use by non-members (e.g. will their friends want to use their installations, would their friends join hcoop, etc.); semi-managed installations vs. manual individual administration; ...

Implement portal redesign: http://hcoop.net/~bpt/tmp/portal.html

Find out whether we can accept copyright assignments

Pass ntk's anti-FISA policy

Moniker TODOs: Keep changes in version control. Reduce wasted white space at top of page. Center HCoop logo.

Policy/guideline ideas:

Licensing policy: (A)GPLv3-compatible for software, the usual free content licenses for other things? We may want an exception for logos, or just protect them as trademarks like Debian does. The content license(s) should ideally be GPL-compatible since we probably have some "content" that is GPL (like domtool docstrings). Relicensing the wiki may be difficult, but there are probably not many (15, 20?) contributors of substantial amounts of currently-relevant text, excluding homepages.

Internal writing guidelines: use gender-inclusive language; promote only FreeSoftware officially, and ask that people consider FreeSoftware principles and the SevenPrinciples when officially recommending a service or organization; write "GNU/Linux" instead of "Linux" when referring to the entire OS


CategoryHomepage

RobinTempleton (last edited 2023-03-20 04:57:01 by RobinTempleton)