ToDo

[JWPlatt]

I have a ToDo list which I might post here for anyone who wants to volunteer to work on any of its line items. It's still a very raw, confusing mess at the moment as I just paste random thoughts into it, so it'll have to wait until it's more coherent.

Mac had a good idea of putting it on JIRA which would allow anyone to easily add their own ideas to get done (and just as easily assign it to someone else - heh!). I recommend getting acquainted with JIRA if you are not already.

We need to set up the "ToDo" JIRA project. But if you have any ideas - line items - about things that need to get done befoer release, post here. Create a new thread for any line item that needs more discussion.

[rarified]

I have started filling in the JIRA template for "Project X", but until I finish the permissions and membership details, please don't post any substantial information to it in JIRA.

I'll post here when it's open for content.

_R

[JWPlatt]

Keep in mind this is more than one project from Cyan itself: client and plugin.

[Mac_Fife]

Within some of the "ToDo" things that have been mentioned (at various times) was bringing the Foundry tools into some sort of stylistic alignment with the more "mainstream" website elements like the forum and wiki.
At the moment, and with what seems to me to be a large amount of work that rarified now has with the exceptional position we find ourselves in, I'd be inclined to say that the "dressing" of those tools should be pretty low on the priority list - Nice to have if we (i.e. rarified) has the time, but hardly essential.

I think user expectation of consistent mastheads and menus in those "specialist" tools is rather lower than for mainstream items like the wiki and forums, so I don't think we'll get the same criticism here that the unstyled forums got in the first months of OpenUru.

[rarified]

I believe I have enough of the JIRA permissions set up for securely entering tasks. I've created three for myself under the Project X project.

You all should have access to Project X, and I've confirmed the demo user does not see it or have access. I'll believe any newly created users and other existing users will be in the same category.

I have created a CWE workflow which is right now a clone of the JIRA default workflow, but I wondered about adding steps such as "requires Cyan approval" and "Cyan approved", "requires Review", etc. Feedback is welcome.

Will work on hooking JIRA to the Mercurial repo as soon as I complete task CWE-3

(Oh JW, I kept one "Project X" and broke it into three components: Server, Client, and Plugin. I think that's a better organization than calling it three projects, at least in our current context.)

_R

[JWPlatt]

Ok, though CWE/Server will be inactive. I think MOSS should be on it's own, and it comes with its own ready-made prefix. That's, uh, MOSS - get it?

[JWPlatt]

I kept one "Project X" and broke it into three components: Server, Client, and Plugin. I think that's a better organization than calling it three projects, at least in our current context.

It sounds good, but last I heard, Components cannot be versioned. That would be not so good.

We need to look up best practices for software suites and consider that things such as documentation and PR are additional parts of any release.

Edit: I found a little blog from NPR about their JIRA setup:
http://www.npr.org/blogs/inside/2010/02 ... rsion.html

[Mac_Fife]

Should there be a Project Admin component in there too, something to go alongside the Foundry Infra, but for things that are outside of rarified's box? There were a few things that JW was suggesting on his embryonic ToDo text file that would be worth tracking. They might have gone in OUORG in other circumstances but they're Project X specific and can't be publicly visible for now.

I don't mind if we decide to use the Infra component instead of creating another, as long as it doesn't mess up _R's plans!

For the time being, I think I'd consider the menu pages for 'Community' and 'Development' to be part of the OUORG SiteNav component: They're public anyway and closely tied to the navigation bar.

[rarified]

I'm fine with adding an additional infra/admin category. I'll do so after I've woken up and taken care of the dog pack. They have little patience once they see me moving in the AM.

[Mac_Fife]

I don't know about anyone else, but I'd really love to see some sort of "good-to-go" status board somewhere. I think we're approaching (I won't say 'fast approaching' because that implies a pressure that doesn't exist) the point where we're going to have to coordinate the Project-X launch event with Cyan. It'd be good to have some visibility of when all our ducks are in a row (or maybe that should be 'when all our squees are in a row').

I'm seeing great progress by rarified on the Foundry thanks to JIRA, and I know where I am on the site design. But I'm not sure what all else is needed. I know a'moaca' is busy doing her thing on MOSS in the background.

There are probably a set of milestones that "enable" Project-X. My view (not necessarily accurate) would be something like:

• Foundry ready
• MOSS ready
• Website ready
• Repos loaded
• Announcements ready

Having an estimated date or green light for these would maybe help us all see whether we're a day, a week or a month away from readiness. If Chogon were to pop up and say "Cyan will be ready to announce next week", it'd be good to be able to quickly say "Yes, we'll be ready, go for it" or "No, we need another week beyond that".