|
Size: 5025
Comment: moniker
|
Size: 3136
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from BtTempleton | |
| Line 3: | Line 4: |
| == 2011 Board Statement == 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 [[http://hcoop.net/~bpt/hcoop/portal.html|redesigning the member portal]]. My platform: * Expand to 150–250 members during the next year and end the pledge system. * Move HCoop accounts to the National Cooperative Bank or a similar credit union. * Implement a strong environmental policy when we are financially able to; purchase carbon offsets to compensate for our use of nonrenewable energy. * Document development processes for our custom software. Recruit more volunteers for system administration tasks. Consider applying to be a mentoring organization for Google Summer of Code 2012. * Last but not least, I will print HCoop T-shirts, finishing the project that NathanKennedy began in 2005. (: == 2010 Board Statement == 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: * 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. * Move HCoop accounts to the National Cooperative Bank or a similar credit union. * Implement a strong environmental policy when we are financially able to; purchase carbon offsets to compensate for our use of nonrenewable energy. * 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. * Last but not least, I will have HCoop T-shirts printed, finishing the project that NathanKennedy began in 2005. (: |
HCoop user bpt; member since 2005, Secretary 2011--present |
| Line 39: | Line 14: |
| Provide more VCS web interfaces: eventually we should have some subset of darcshub, darcsweb, hgweb, gitorious, cgit, extended gitweb, maybe even Sourceforge or Savane Next meeting: sign the [[http://www.internetdeclaration.org/|Declaration of Internet Freedom]] and register as a stakeholder in [[https://gnu.org/consensus|GNU/consensus]] Set up an independent MeetBot instance. |
Provide more VCS web interfaces: eventually we should have some subset of darcshub, darcsweb, hgweb, gitorious, cgit, extended gitweb, maybe even Sourceforge or Savane (or, as of 2016, Gitlab/Kallithea/gogs/...) |
| Line 53: | Line 24: |
| Go to FOSS Fair: https://opensource.ncsu.edu/FossFair2013 Research registered agents; Incorp requires that we use a proprietary, Windows-only Silverlight program to pay the annual fee |
|
| Line 65: | Line 32: |
| 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. | 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 be GPL-compatible since we probably have some "content" that is GPL, like domtool docstrings. (CC-BY-SA 4.0 is one-way compatible with GPLv3.) Relicensing the wiki may be difficult, but there are probably not many (15, 20?) contributors of substantial amounts of currently-relevant text, excluding homepages. |
| Line 69: | Line 36: |
| [[https://utcc.utoronto.ca/~cks/space/blog/web/TLSSuicideAndUserCGIs|One good reason not to allow .htaccess:]] it's apparently difficult to control which HTTP headers can be set by users |
HCoop user bpt; member since 2005, Secretary 2011--present
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 (or, as of 2016, Gitlab/Kallithea/gogs/...)
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
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 be GPL-compatible since we probably have some "content" that is GPL, like domtool docstrings. (CC-BY-SA 4.0 is one-way compatible with GPLv3.) 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
One good reason not to allow .htaccess: it's apparently difficult to control which HTTP headers can be set by users