| User | Post |
|
12:02 am
October 16, 2010
|
Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
As part of our new momentum burst and effort to get things running more smoothly, maybe we should talk about how we're going to modify our web infrastructure as we move to the new project/program set, etc.
At the moment we are using:
- Wordpress for overall site management, including static pages and a blog
- These forums to do our engineering work
- A Wiki to store the results of engineering work and also to host some fairly static pages (Social Contract, etc)
This probably isn't the most efficient way of doing things. Let's see how we can improve.
Obviously, all engineering related stuff should eventually be migrated under the ODE application (and we're currently talking about choosing an off the shelf application to use as the base for this).
Once this is done, do we want to keep the forums and/or Wiki, and if so, what should they be used for?
I feel like a lot of stuff which is currently in the Wiki should really be moved to the website proper, i.e. into Wordpress. The Mission Statement, Social Contract and Design Philosophy are obvious examples. All the projects/programs should have landing pages on the website (as discussed and already mocked up), and those should link to relevant ODE pages to provide more detail.
If the forums hang around I think we should keep them fairly informal and have far fewer subforums etc. All technical discussion can happen in ODE and whatever methods it provides for communication. The Wordpress forums could, perhaps, serve for new member introductions, suggestions on things like fundraising, etc.
I'm not really sure what role the Wiki should play in future. With the Social Contract etc. moved to the website where they really belong, and engineering material being stored in ODE, there doesn't necessarily feel like a huge need for it. Maybe as a repository for non-technical details related to projects? i.e. things like CAD diagrams and circuit schematics belong firmly in ODE, but maybe each time we do a rocket test fire or a balloon flight we could put a page in the Wiki with a summary of what happened and some pictures, etc? I feel like that sort of stuff is out of place in ODE.
Finally, we should think again about document management. Some documents are going to be fairly closely linked to particular projects/programs, and they can probably go in ODE. But quite general technical reports, on things like orbit simulation or reentry modelling, can probably go in their own separate system. We should choose or write a system to do this, I think.
All input welcome. Let's try to come up with a new web infrastructure which will work a lot better for us than what we have now.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
12:36 am
October 16, 2010
|
Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
Something I've thought for a while: it would be kind of cool if we could have something like a "private del.icio.us" app running at cstart.org for people to submit links to. Does anybody know if something like this exists?
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
10:53 am
October 18, 2010
|
antinode
| | |
| Member | posts 64 | |
|
|
I mentioned the concept of "groups" in another thread…
"I'd like to propose the addition of non-project specific "groups". For
instance, a communications group. Anyone interested in communciations
could join this group and participate in non-project specific discussion
related to communications, submit relavant URLs, etc. Contributors in
the Communications subsystem teams of each project could collaborate in
this group."
Groups could replace the non-project specific forums, and provide the ability to submit relavant links, similar to delicious and Facebook. There could be a "PR" group, and a "finance/fundraising" group.
I think that mission summaries should be in the ODE. Both with detailed data in project wiki, and a simple overview with photos in the project blog. Notable project blog posts can be simul-posted on the main site blog.
I'd like to see the wordpress blog replaced with an ODE-based blog to facilitate this, as well have the static pages (Mission Statement, etc) replaced with ODE-based themed wiki pages only editable by a handful of people.
I'd like to see the ODE integrated as much as possible. Having everything handled by a single framework, with a single user list, and proper user roles and permissions, is the proper way to go about this.
|
|
|
9:19 pm
October 29, 2010
|
Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
I'm not sure what I think of some of those suggestions.
One the one hand, I can absolutely see the appeal of a single system with one uesr list and one set of roles/permissions. That will just be so much easier than the alternative, both for the people building the software and the people using it.
On the other hand, I really am not sure that things like mission summaries, blogs, etc belong in the ODE framework. ODE is supposed to be a general purpose application-neutral platform for designing open hardware. It might be appropriate to have some kind of news-related functionality in there, but anything too CSTART specific (i.e. anything which makes any reference to our program/stage/project/mission hierarchy) shouldn't get in. I suppose if we were to implement things like mission summaries etc. using tools like blogs and wikis that would be okay. Although you mentioned using wiki pages for CSTARTy things like the Mission Statement…those wouldn't belong in any wiki which was attached to a particular project. Were you envisaging ODE having a general project-independent wiki in it in addition to the per-project wikis? Does that make sense?
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
10:57 pm
October 29, 2010
|
Nick
| | Florida | |
| Member | posts 34 |  
|
|
|
What is the current status on the ODE? I havn't heard much.
|
|
|
|
|
11:19 pm
October 29, 2010
|
Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
ODE doesn't exist yet as anything more than a collection of ideas and basic requirements. Pretty much all the discussion of it is in this thread.
The current arc over there is aimed at choosing an existing off-the-shelf package to use as a base for ODE, so that we can install that base ASAP and use it to begin work on the newly named programs. For example, there was some really good design work going on for Cloudlab on the forums a while which it would be great to start importing into ODE, so there is good reason to want something now rather than in a few months when we've got something basic built from scratch.
Not much work has gone on so far with regard to choosing a base, though.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
11:37 pm
October 29, 2010
|
Nick
| | Florida | |
| Member | posts 34 |
|
|
|
What are some of the ideas tossed around as far as the base system?
|
|
|
|
|
12:27 pm
October 30, 2010
|
antinode
| | |
| Member | posts 64 | |
|
|
Luke Maurits said:
On the other hand, I really am not sure that things like mission summaries, blogs, etc belong in the ODE framework. ODE is supposed to be a general purpose application-neutral platform for designing open hardware. It might be appropriate to have some kind of news-related functionality in there, but anything too CSTART specific (i.e. anything which makes any reference to our program/stage/project/mission hierarchy) shouldn't get in. I suppose if we were to implement things like mission summaries etc. using tools like blogs and wikis that would be okay. Although you mentioned using wiki pages for CSTARTy things like the Mission Statement…those wouldn't belong in any wiki which was attached to a particular project. Were you envisaging ODE having a general project-independent wiki in it in addition to the per-project wikis? Does that make sense?
I was using the term ODE quite generally as the site backend, not as the standalone hardware project management app. I was speaking of a version modified to suit CSTART's needs. The ODE is the most important aspect of the site, but it'd be best to use a similar codebase and user management for the rest of the site, rather than having a wordpress blog, a wikimedia wiki, and ODE project management used for each project. Seeing as how certain missions within a program would require use of multiple projects, maybe it'd be best to have program pages that give the program overview, that programs missions and mission details, and the projects (ODE) of that program. That way mission blog posts and mission data would be seperate from the "ODE".
When I mentioned using wiki pages for things like the Mission Statement I meant using the same wiki-backend as used in the ODE, with user permissions and file history, rather than having static HTML pages. So yes, a project-independant wiki of sorts, but not visibly a wiki to non-admins and themed to not look like a wiki.
Nick said:
What are some of the ideas tossed around as far as the base system?
They're mentioned in the thread that Luke linked to but current contenders are the Ruby based Redmine, or one of two Python based Trac forks, DrProject or Basie. Seeing as how all suit our initial needs, and nobody seems to know Ruby, I'm strongly leaning towards one of the Python options. Since nobody seems to be making any decision, I'll likely start work on one of the two in the next few days.
|
|
Login 
Register 
Search 
Home
Topic RSS 
