Difference between revisions of "WebComTODO"

From OSGeo
Jump to navigation Jump to search
(New)
 
(Redirected page to Archived)
 
(57 intermediate revisions by 13 users not shown)
Line 1: Line 1:
List of tasks to be done by Web Committee.  Eventually I imagine this should be handled by the bug (artifact?) tracker but I don't know how to use that properly yet.
+
#REDIRECT [[Archived]]
  
 +
= General Direction =
  
== Frank's Suggestions ==
+
== Transition Related ==
  
=== Short Term ===
+
* Approve and post a Privacy Policy.  We used to have one similar to http://www.jxta.org/nonav/servlets/LegalNotices?type=PrivacyPolicy on the old site, and might want to emulate it.  
# Update the [[OSGEO Website Terms of Service]] on the web site.  
+
* Provide some mechanism for feedback for the websitePerhaps a "feedback" link that suggests email to info@osgeo.org?
# Setup mechanism for people to create accounts website user accounts on their own.
+
* Do we need a "terms of use" documentI'm not sure what happened to our old terms of use, but they were partly collabnet oriented.
# Setup WebCOM mailing list, and get committee members on it!
 
# Setup feedback mechanism for web siteI suppose this ought to be creating artifacts in the bug system, but a feedback email list might be more appropriate.  
 
# Recruit more members on discuss list.  What skills are are most valuable?   
 
  
=== Medium Term ===  
+
== Current Work ==
# Setup WebCOM web page, with "mandate" and policies and procedures. 
 
# Work on web site overall style.
 
# Ensure that WebCOM members can update all appropriate web pages (ie. osgeo.org, webcommittee.osgeo.org, board.osgeo.org, etc).
 
# Hold an OSGeo Logo contest.
 
# Flesh out the web site pages.  New, about, contact, etc.
 
# Setup wiki.
 
  
=== Wiki ===
+
* Flesh out the generic web site pages.  New, about, contact, etc.
# Figure out a wiki technology to incorporate.   Mediawiki seems really nice.  The Java folks seems really keen on Confluence.
+
* Set up site structure to provide Compass-like navigation
# Do we need this hosted on a non-collabnet server since it isn't a core collabnet service? 
+
* Develop Content
# We need some mechanism(s) to ensure the folks realize material in the wiki is not authoritative.  That it is essentially individuals working documents, not foundation policy.  
+
** [[Why Open Source Geospatial]]
# Make sure the wiki requires some sort of login or something so it is not easily spammed.
+
** [[How Can I Help]]
 +
** [[Who is OSGeo]]
 +
** [[What is OSGeo]]
 +
 
 +
== Pending ==
 +
 
 +
* Work on web site overall style. (waiting for decision on tech infrastructure)
 +
* Organize translation volunteers. (need technical infrastructure for multilang support)
 +
** [[Portal Translation Status]]
 +
 
 +
=User-submitted tasks=
 +
 
 +
==Submitted==
 +
 
 +
* Any exisiting or future OSGeo [[Membership Application]] webpage needs to include a "Member Responsibilities" section along with a mechanism(e.g. checkbox) to indicate explicit acceptance of those responsibilities. Existing "Members" should have to edit their membership to also indicate acceptance. This is so that if the " Membership Change and Revocation" issue as mentioned in the [[Proposed_Membership_Rules]] ever arises the Board knows that the Member did agree to 'the rules'.
 +
 
 +
==Approved and Pending==
 +
 
 +
==Completed for Review==

Latest revision as of 23:12, 6 May 2018

Redirect to:

General Direction

Transition Related

  • Approve and post a Privacy Policy. We used to have one similar to http://www.jxta.org/nonav/servlets/LegalNotices?type=PrivacyPolicy on the old site, and might want to emulate it.
  • Provide some mechanism for feedback for the website. Perhaps a "feedback" link that suggests email to info@osgeo.org?
  • Do we need a "terms of use" document? I'm not sure what happened to our old terms of use, but they were partly collabnet oriented.

Current Work

Pending

  • Work on web site overall style. (waiting for decision on tech infrastructure)
  • Organize translation volunteers. (need technical infrastructure for multilang support)

User-submitted tasks

Submitted

  • Any exisiting or future OSGeo Membership Application webpage needs to include a "Member Responsibilities" section along with a mechanism(e.g. checkbox) to indicate explicit acceptance of those responsibilities. Existing "Members" should have to edit their membership to also indicate acceptance. This is so that if the " Membership Change and Revocation" issue as mentioned in the Proposed_Membership_Rules ever arises the Board knows that the Member did agree to 'the rules'.

Approved and Pending

Completed for Review