Difference between revisions of "WebComTODO"

From OSGeo
Jump to navigation Jump to search
m
(Redirected page to Archived)
 
(28 intermediate revisions by 11 users not shown)
Line 1: Line 1:
List of general TODO items for the Web Committee. 
+
#REDIRECT [[Archived]]
For specific tasks, please submit a detailed explanation
+
 
  of the work to be done to our [https://webcommittee.osgeo.org/servlets/Scarab Project Tracker]
+
= 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 ==
 
== Current Work ==
  
* Flesh out the web site pages.  New, about, contact, etc.
+
* Flesh out the generic web site pages.  New, about, contact, etc.
* Copy IRC logs from the Feb meeting (http://logs.qgis.org/geofoundation/) into the https://www.osgeo.org/content/foundation/meetings/2006_02_04/meeting.html area.
+
* Set up site structure to provide Compass-like navigation
 +
* Develop Content
 +
** [[Why Open Source Geospatial]]
 +
** [[How Can I Help]]
 +
** [[Who is OSGeo]]
 +
** [[What is OSGeo]]
  
 
== Pending ==
 
== Pending ==
  
=== Short Term ===
+
* Work on web site overall style. (waiting for decision on tech infrastructure)
* Setup feedback mechanism for web site.  I suppose this ought to be creating artifacts in the bug system, but a feedback email list might be more appropriate.
+
* Organize translation volunteers. (need technical infrastructure for multilang support)
 +
** [[Portal Translation Status]]
 +
 
 +
=User-submitted tasks=
 +
 
 +
==Submitted==
  
* [[Logo Contest]] Sent to board, waiting approval before posting to site. Perhaps VisCOM should be doing announcements, etc?
+
* 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'.
* Recruit more members on discuss list. What skills are most valuable?
 
* Fix typos at https://mail.osgeo.org/; also define "member" there ("discuss is for members only") - I guess we want many subscribers...
 
  
=== Medium Term ===
+
==Approved and Pending==
* Work on web site overall style.
 
* Organize translation volunteers.
 
  
=== Wiki ===
+
==Completed for Review==
* 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.
 

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