Subscribe to rss feed

We have our Wiki! Now how should we use it? | Project management | Forum

 
You must be logged in to post user permissions login Login register Register


Register? | Lost Your Password?

Search Forums:


searchicon 






Minimum search word length is 3 characters – Maximum search word length is 84 characters
Wildcard Usage:
*  matches any number of characters    %  matches exactly one character

topic

We have our Wiki! Now how should we use it?

print
small tagNo Tags
UserPost

6:52 pm
November 17, 2009


Luke Maurits

Adelaide, Australia

Admin

posts 1483

offline
link
print
1
0
ratedowngrey
rateupgrey

We now have a Wiki hosted at cstart.org and linked to from the main navigation bar.  Big thanks to Zvan for all his web related work!

While we're waiting for the contents of brmj's temporary Wiki to be migrated over, let's figure out how we're going to use the Wiki, from the point of view of who has permission to edit what, and what goes where when.   My thoughts have been something like this, and I welcome feedback:

Most of the central pages in the Wiki (i.e. the main pages for CSTART, CLLARE, Selene, each of the workgroups, etc) should be locked so that they may only be edited by administrators.  Actual design decisions etc. will made by the crowd in the forums, which will be a free-for-all, in the sense that anybody can post anywhere.  Part of the role of workgroup representative (who will have admin priveleges on the Wiki) will be to make regular updates to the relevant parts of the Wiki when consensus is reached in the relevant parts of the forum.  Basically, the forums will be a frothing mass where ideas and plans are in some kind of turbulent mixing; as small patches of this sea of ideas crystalise and become fixed, they will be copied over to the Wiki by an admin.

There will need to be some sort of procedure to prevent admins are Wiking stuff too quickly and effetively making decisions themselves: perhaps workgroup reps will have the power to post polls to the forum when they feel like a consensus is close to being reached, and then they may only Wiki the ramifications of that consenus across if the poll shows greater than 75% support from a sample of at least 10 people (actual numbers may vary).  This introduces the problem of reps refusing to post a poll if they feel a decision is going to go against their preference – for now we can probably guard against this well enough by having more than one rep per workgroup.

Under the above view I imagine anybody being able to create Wiki pages – this way factions within the forum have a place to sketch out their ideas, post data, etc.  Since they can't edit main pages of the Wiki, there will be no prominent links to these temporary parts of the Wiki – they will only really be seen by people active in the appropriate parts of the forum.  As decisions are made, Wiki admins can link to temporary parts of the Wiki when and if they become canonised.

Does anybody have any thoughts on this approach?

Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.

8:41 pm
November 17, 2009


Rocket-To-The-Moon

Altus, Oklahoma, USA

Member

posts 685

offline
link
print
2
+1
ratedowngrey
rateupgrey

Post edited 2:43 am – November 18, 2009 by Rocket-To-The-Moon


I'm not a big fan of locking down the privileges of users. I can see only letting registered users make edits (no anonymous users), but only allowing admins to make edits to the main pages creates a large burden for these users while distancing others from the core of the project. If a particular page becomes overly controversial then we could lock it so that only administrators can make changes. To me this seems like a step away from being an open project. It will also turn it into a chore for the admins which will tend to put them off. Using Wikipedia as an example, I think that everything will fall into place after x number of revisions.

I can see locking pages several years down the line once things are starting to fall into place, but for now we need all the help that we can get.

You very well may have the correct idea though, maybe this is a necessary bureaucracy layer that we need.

I can understand where you are coming from though, using my edits yesterday as an example of a single user making decisions (naming ect.).

Main Workgroups: Propulsion & Spacecraft Engineering

5:50 am
November 18, 2009


Luke Maurits

Adelaide, Australia

Admin

posts 1483

offline
link
print
3
0
ratedowngrey
rateupgrey

I take your point about heavy restrictions being somewhat antithetical to the whole open collaboration ethos.  I suppose I am erring on the side of caution with regards to things like vandalism or hijacking of decisions (as an aside, please don't think I'm trying to single out your naming posts the other day as some kind of example of a problem!) – I don't really have any experience with large collaborative projects like this some I don't have any intution as to how much structure is required to keep things together.  Idealistically, I'd like things to be as close to anarchy as they can be without it impacting the quality or reliability of our work.  Perhaps we should start with a completely open Wiki (except no anonymous edits) and only move to a stricter admin-based system if it appears to be necessary.

Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.

small tagNo Tags

About the CSTART – Collaborative Space Travel and Research Team Forum

Forum Timezone: UTC -6

Most Users Ever Online: 59

Currently Online:
10 Guests

Currently Browsing this Topic:
1 Guest

Forum Stats:

Groups: 4
Forums: 36
Topics: 512
Posts: 3809

Membership:

There are 1133 Members

There are 2 Admins

Top Posters:

Rocket-To-The-Moon – 685
brmj – 402
rpulkrabek – 348
DenisG – 69
antinode – 64
J. Simmons – 46

Recent New Members: jmwright, uhwuggawuh, seikialice88, bishvabis, alijayadv, harris

Administrators: Luke Maurits (1483 Posts), Rizwan (170 Posts)



 
share save 120 16