Saturday Mar 06, 2010
Thursday Feb 25, 2010
By jimgris-Oracle on Feb 25, 2010
Reminder: when we moved from the old tonic database to the new auth.opensolaris.org application for account management, all users had to verify their accounts on the new system. That involved logging in, following a couple of prompts, and saving. That's it. Painless. Multiple mails were sent to everyone. But, as is human nature, a few people have still not validated their accounts. So, if you haven't verified your account on the new system, you are now in the Inactive state and that means you won't be able to log in or put back code or vote or post to the forums or edit the site. Just ping website-admin at opensolaris dot org and we'll reset your account. That's a private list, by the way, and we have people in the US, Europe, and Asia managing user accounts so mails only sit on that list for a very short period of time.
Tuesday Feb 23, 2010
By jimgris-Oracle on Feb 23, 2010
This is very cool. Robert Antoni, who is a contributor in the OpenSolaris Internationalization & Localization Community, posted mail to website-discuss and i18n-discuss about a really interesting contribution. He localized the XWiki application resources file
into the Catalan language. So after that contribution is integrated
into XWiki, we'll be able to pick it up when we update our
implementation of XWiki as well. And that will help the OpenSolaris
community localize opensolaris.org into Catalan. So, both communities benefit from Robert's contribution. Really excellent.
Auth is already available in the Catalan language, and the new SCM Console will be as well when we deploy sometime in March. It will be good to have the underlying XWiki interface localized as well.
More information about contributing:
Monday Feb 22, 2010
By jimgris-Oracle on Feb 22, 2010
To make formal voting on the OpenSolaris project painfully easy, Bill
has been updating the voting application
and he deployed
the new version today. Voters will no longer need SSH keys
since poll is now integrated with the auth database, and voting will be
done via a
new web front end with encryption so the command line is no longer necessary. Those were
the two main complaints previously. So, now voters can just go to poll.opensolaris.org,
a poll (if you are not logged in the system will prompt you to log in),
and then point/click on a ballot. Easy.
Poll will be available to current Core Contributors (see recent audit and database clean up mail) for testing for one week. I updated the website project's announcements and roadmap pages. Here is information on all the 15 applications that make up opensolaris.org.
Friday Feb 12, 2010
By jimgris-Oracle on Feb 12, 2010
Tuesday Feb 09, 2010
By jimgris-Oracle on Feb 09, 2010
- New public information screens displaying much more detail about user, collective, and governance relationships (these screens will be accessible via each XWiki Collective in the near future as well).
- The ability to download the data from the public info screens in multiple formats.
- New screens in each private user account displaying summary data from all the user's relationships with start and end dates.
- The addition of eight languages (so Auth is now localized into 25 languages).
- Some miscellaneous bug fixes and probably some stuff I missed.
And finally there has been a bit of confusion on some lists recently about how the community is organized and the various roles/rights people have on the site. If anyone has any questions, please read the Roles & Collectives document first. It's the only document on the site that explains all the roles and all the collectives and all of the website and governance privileges. Send questions to website-discuss.
Tuesday Feb 02, 2010
By jimgris-Oracle on Feb 02, 2010
Tuesday Jan 26, 2010
By jimgris-Oracle on Jan 26, 2010
Spent some time cleaning up the content in the Website Community
yesterday. The transition to auth/xwiki is over, so I rewrote a lot of
the content we had pointing to the project management docs and moved
some content to archive to clean up the nav. I cut the amount of
content on the top level page in half. Roadmap & Announcements
updated too. Over the last few months, we've accumulated a huge amount
of information about the website project and various community
processes. Still streamlining. Next needs to address the front page of the site.
Friday Jan 22, 2010
By jimgris-Oracle on Jan 22, 2010
Sunday Jan 17, 2010
By jimgris-Oracle on Jan 17, 2010
The latest version of auth.opensolaris.org is now in the Community Translation Interface for a localization update, and we are also now starting to localize repo.opensolaris.org as well. Because of many community contributions recently, auth.opensolaris.org already lives in 17 languages. It will be good to get the SCM Console at repo.opensolaris.org localized into a bunch of languages via the same process as we continue updating that application in the coming months. See the announcement from Ales on i18n-discuss for details about contributing to these these two website projects.
The localization of opensolaris.org -- which is
currently 15 applications -- will come together over time and in
various stages. But I really would like all of it localized into at
least two dozen languages by the end of this year. Should be doable.
So, if you are interested in participating, I wrote an outline about
how we are breaking this into pieces and how you can get involved: Localizing
Website Content. I will update the document as the project evolves.
See the Internationalization
& Localization Community for even more projects and
to i18n-discuss. Thanks.
Saturday Dec 19, 2009
By jimgris-Oracle on Dec 19, 2009
Since the transition to the Auth and XWiki applications in August and October, the website team has been updating (editing, deleting, moving, merging, rewriting) the majority of common content on the site -- all the stuff around the edges, the stuff not in Communities, Projects, User Groups, or Subsites. We're making good progress on these updates now as well as maintaining various project management documents for the website transition. Here is the initial list of two dozen files we updated recently. More coming. Send questions/suggestions to website-discuss. File bugs at defect.opensolaris.org.
Here are the most important content updates in this round:
Roles & Collectives (Updated):
Start here to understand the context around all of the roles in all of the collectives on the site (including the elusive Electorate) and who has Website Privileges, Administrative Privileges, Source Code Repository Privileges, and Governance Privileges. It's all on one page.
User Guide (New):
An outline of the essential tasks most users perform on the site based on the roles they hold and the collectives in which they participate.
Website Content (New):
An emerging contribution model to translate all the content on the website.
Infrastructure Life Cycles (Updated):
How community members can acquire new website infrastructure, and how that infrastructure is managed throughout various life cycles. All the spaces on the site have slightly different acquisition processes, but everything is documented on one page.
- How to
There are many ways to participate in the OpenSolaris Community. Advocate for the community, contribute code, report bugs, translate content, help new users get involved, port and maintain packages, write documentation, start user groups. How would you like to participate? Tell us.
After the winter break, we'll address more content issues (including the front page of the site), we'll deploy significant updates to the Auth and XWiki applications (both are being tested now), and we'll start working on some graphical and navigation issues across the site. Looking forward to it. We're making solid progress now, and we have a pretty good plan to continually evolve the site to support OpenSolaris engineering operations and community development programs around the world.
Thursday Dec 03, 2009
By jimgris-Oracle on Dec 03, 2009
Now that we've moved to XWiki, we should
about the business of
localizing more of the OpenSolaris website. This is going to take a
it will require work from the community and from the website
engineering team. It may also require some people from Sun and the
OpenSolaris community getting directly involved in the XWiki community,
which could prove interesting as the communities
benefit from each other's contributions. It's a big opportunity all
around, and hopefully we'll be able to build more OpenSolaris
development communities around the world by simply speaking more
languages on our website. There will be multiple steps involved to
localize everything, but at least we have some tools in place and a
much better platform from which to build some interesting localization
projects. So, here are the big three buckets:
1. AuthAuth is already localized into 17 languages thanks to the contributions of the OpenSolaris community using the Sun Open CTI tool. In a few weeks, we will update auth, and then after that the community will be able to update the localizations for auth as well. The process of localizing auth is well known now, and we'll just move ahead as we have in the past. Auth is most important in this process because the more languages we can localize auth.opensolaris.org into the more languages we can offer on our implementation of XWiki at hub.opensolaris.org. Remember, hub is integrated with auth and part of that integration means that language preferences are set in auth.
2. XWikiXWiki currently supports 21 languages in the base application. Now, if you go to the OpenSolaris website and edit a page, you will see the following text in the right navigation bar:
Document translationsHere's what it looks like in a screen shot. Those eight languages represent the intersection between localizations supported on auth.opensolaris.org and those supported by the XWiki application itself. It's important that we build out that intersection so we can enable more languages on hub.opensolaris.org for the community to localize more general OpenSolaris content. So, when you click on a language code in that nav, certain elements on the screen will immediately change to that language, and the URL will change to language=[whatever language you chose]. After you translate and save the page, the right nav bar in edit mode will display the language code, and also at the top right side of the page the new language code (among whatever other translations are there) will display with a little flag icon. That tells users the page is localized into any number of languages. Pretty basic but we didn't have this capability on the old site.
You are editing the original document.
Translate this document in: cs de en es fr pl ru zh
Now, here's the challenging and/or confusing part from a social point of view. hub.opensolaris.org is not a wiki where anyone can edit and translate anything. The site is actually comprised of many applications and many spaces, but all of the content basically fits into three big sections:
- Common Content: This content includes the front page, project overview, FAQ center, roadmaps, site map, downloads, Collectives overview and navigation, navs, header/footer spaces and documents, style sheets, etc. Sun's Website Team manages the common content on hub.opensolaris.org, and requests to update and translate this information can be made on website-discuss. Contact information here.
- Collective Content:
we built into the new site, and that should be enough to explain the basic structure without having to read the entire Constitution. Basically, if you have edit privileges to your own areas on the site and you want to translate some content, then go translate content. Just do it. But if you want to translate content in an area of the site where you don't already have edit privileges, then you should contact the Leaders in those areas and ask them if they would be interested in having their stuff localized and if they would give you the appropriate editorial privileges to do that work. Can you imagine people saying no to that request? I can't. And the manual process of going out and talking to people will only increase the number of interactions community members will have with each other. That can only be good.
3. SubsitesThe subsites should to get localized at some point, too. This can be accomplished in three steps:
- First, the website engineering team will build a backend web
application to serve all the common graphical elements of the
OpenSolaris website to
all the subsites, so that includes the headers, footers, wordmarks,
logos, icons, etc. This way, the entire website can have a common look
and feel (as much as
possible given that there are many applications involved). Also, the
benefit of this concept becomes clear when we have to update common
the site or add new translations or templates. Then all of the subsites
updated as well and those owners don't have to worry about keeping in
sync with the rest of the site. Over time, all of the sites that make
up opensolaris.org will look and feel more like one site (with single
sign on via auth, of course). That's the goal anyway.
- Second, the OpenSolaris community will be able to localize all the content for that web application, and when we are ready we'll make it available via the Open CTI tool. So, even embedded text in icons will be translated.
- Third, OpenSolaris community members can contact the subsite owners and offer to translate that content, which can then be uploaded to each subsite by the Leaders.
Contribute Right NowSo, to sum up a bit, if you have language translations skills, here's how you can contribute to this crazy website localization effort:
- Localize content in the areas that you already have privileges to
- Ask other Leaders in other Collectives if they would like you to
localize their content.
- If you are a Leader of a Collective and you are not involved in
localization and want your content translated, post to i18n-discuss
and ask the Internationalization
& Localization Community.
- Ask the Website Team if they`d like the common content on the
site localized. The answer
is yes, by the way. We have updated a great deal of the site's
common content (FAQs and such), and we continue to do so. So check with
us first so we can remain in sync as much as possible.
- Add more languages to auth
CTI by translating the auth resources file. Ask questions on
here, forum here,
A new auth resources file is coming soon.
- Add more languages directly
to the XWiki application at l10n.xwiki.org by translating the XWiki
ApplicationResources file. NOTE: WE NEED A JAPANESE
TRANSLATION OF THIS FILE! It's a big deal and would represent a
gigantic contribution to the XWiki community as well as the
OpenSolaris community. I am talking with the XWiki community
about this as well (see
thread beginning here and running about 15 messages).
Currently, XWiki does not support Japanese (ja)
among its list of 21 supported languages (it supports Japanese language
text displayed on pages, of course, but not at the application
with menu and icons and the URL). Subscribe to the
xwiki users list here.
- Content translations are major contributions to this community.
We take them seriously. Please read and sign the Sun
Contributor Agreement (FAQ here),
so everyone's rights are understood and protected. Here's more on contributing
What do you think? I certainly don't have this all figured out yet, but that's enough to start. On the old site, we started this project with the Portals, but that was a very temporary effort to fix a site that didn't support localization. Auth and XWiki do support localization (see XWiki's application evaluation here), so now we can move much faster on these early steps. Even longer term, we'd like to develop a system to automate some of this so we can do bulk translations and publish those documents automatically. One thing at a time
Tuesday Dec 01, 2009
By jimgris-Oracle on Dec 01, 2009
A couple of weeks ago we had a conversation on website-discuss (here, here) about some features of the new website that were not directly moved and/or replaced from the old site. Much of the discussion involved blogs. Put simply, blog aggregation on the site changed because the website application changed. We migrated to an entirely new application, one that offers substantially more benefits over the old one. But as a result, some of what was on the old site was not replaced (or may be replaced in new/better ways in the future). One item on that list was the old (badly broken) blog aggregation system we had at the top level of the old site. Some people have been concerned that we no longer have the ability to collect blogs on the new site. Not true. Here's a better way to look at it:
Before the migration to XWiki:
opensolaris.org used to have three levels of blog aggregation: (1) blogs collected at the top level of the site, (2) blogs collected inside Community and Project spaces, and (3) blogs collected at planet.opensolaris.org. That was nice, I suppose, but probably a bit over the top. Also, the processes for deciding what blogs to aggregate was distributed among the owners of each of the spaces on the site, all the mechanisms to collect the feeds were manual, and community members had no way to offer their feeds into a centralized database. But we poked along with what we had.
After the migration to XWiki:
The new opensolaris.org does not have a top level blog aggregation feature. But Collective Leaders, Affiliates, and Developers can still add blog feeds to their Communities, Projects, and User Groups and planet.opensolaris.org remains the same as it always has been. Also, we are exploring ways of providing a centralized blog feed directory via the site's new Auth database, so that blogs can be easily aggregated in Collective spaces or on planet.opensolaris.org or externally with whoever wants them. I like this idea a lot (via Alan Burlison) because it keeps the decision making process of what feeds to collect directly with the people closest to the action: Collective Leaders.
I do not support a top level blog aggregation system for all blogs in the OpenSolaris world because before you know it you have thousands of blogs, most of which have owners who are not necessarily directly involved in the community on the site. Then it all becomes too big and the value drops rapidly. It's too much centralization. That's what happened with the old system. And although some people have complained that they miss the old feature, I got a heck of a lot more complaints about it when it was live. Complaint #1 was that I was taking any blog off the street that mentioned OpenSolaris in any way whatsoever and that was diluting the overall content too much because too many of the bloggers weren't really involved in the community. Point taken. Also, I don't support the notion of screening blogs at the top level of the site because that makes the website team judge and jury as to who gets collected -- and that is most certainly not our role. We should be pushing content and projects and decisions into the Collectives where people are actively working their stuff and where they have edit privileges to their own spaces on the site.
Anyway, in the mean time, Collective Leaders, Affiliates, and Developers can add blog feeds via the XWiki RSS macro. Just edit a page, click on the macro tab at the top left of the edit box, scroll to select the RSS macro, and enter the data in the fields provided.
By jimgris-Oracle on Dec 01, 2009
It's amazing how fast content goes stale. Man. Just give it a little time and it's toast. Fortunately, now that we are running XWiki it makes updating stuff jet fast (and it will be even better when we move to XW2). I like XWiki markup, too. It's just simple.
I updated about 20 pages with little nits here and there last week, and the more I look the more I find in need of updating. Over the next couple of weeks we have to update the FAQs, Roadmap, and Website Project substantially to give people a better idea about the current website plans now that the Auth and XWiki transitions are complete. More on those later.
I rewrote the Contacts and Help pages, too. I think these pages should be merged, though. I don't see any need to have both, but since they are currently separate I tried to write around that for now.
And, of course, the OSUG leaders table
remains in constant motion. I added several new OSUGs this last week or
so. User Groups come and go in waves, but the OSUG community remains
one of the most active groups on the entire site.
I also updated the Collective Life Cycle Instructions with a lot more detail and some important footnotes (especially the need to choose unique names for Collectives and the distinction between names and titles). The more I set up Collectives on the new site the more I find to document. Website infrastructure can be activated, deactivated, reactivated, transitioned, and terminated so I flushed out the document with more specifics for community leaders going through each phase. I am trying to make that document comprehensive so at least we have one place to send people for everything related to Collective life cycles. Even after the transition to the new site, which involved deleting and merging many documents, we are still way too fat on opensolaris.org. We have too many overlapping process documents that confuse people, so we are still trimming those down. Making progress.
Friday Nov 20, 2009
Monday Nov 02, 2009
By jimgris-Oracle on Nov 02, 2009
I will be starting to set up new Collectives on XWiki later this week.
For the past few months we've had a temporary moratorium on creating
new infrastructure on the site due to the website transition. The
interim period was way longer than we expected. Apologies for that.
I'll clean out the queue this week in the order in which the requests
came in over the past few months. Also, if you have been waiting to
submit Collective proposals to your Community Groups for new Projects
or User Groups, please feel free to move ahead now. The same applies
for new Community Groups getting approval from the OGB. I only get
involved in this process on the implementation end, and everything you
need to know about that is documented here: Collective Life Cycle Process.
Tuesday Oct 27, 2009
By jimgris-Oracle on Oct 27, 2009
We finally moved to XWiki last night. I sent the
out around 4:15 my time this morning. It was a long day. I have been
sick for a couple of
weeks, so that marathon last night didn't help things much. But we went
out and we didn't blow up. Cool. This is
Phase 2 of the website transition. Phase 1 was the development and
deployment of the Auth user management system and the merging of the
tonic and poll databases all around a governance structure. Among other
things. And now this Phase 2
represents the customization of XWiki and its integration with Auth and
the migration and translation of the old tonic website content into
XWiki. Among other things. The
sequence is actually pretty substantial.
The team working on this thing yesterday was spread out all over the
world -- Boston, Colorado Springs, San Francisco, Manchester, and
Tokyo. Some of us were up at 4 in the morning, while others stayed up
till 5 in the morning the next day. The final migration took somewhat
longer than expected because we had to fix critical issues (networking,
performance, redirects, etc) as we went
live while under real loads for the first time. We had
done 31 migrations in 3 months to give ourselves and everyone in the
community enough time to prepare, but going live always draws new
to deal with. It turned out ok, though. And the performance has been
very good so far (and this will improve as we further optimize the
application). Anyway, not bad for a v1 attempt. And that's exactly what
this is. A start.
But it feels good to be living in one world now, instead of having to go back and forth between vastly different website architectures resolving differences between the two -- all while maintaining current operations on an old site that was quite literally at the breaking point. That last part was a very big deal in this gig, and far too many people still don't realize that that was hanging over our heads the entire time. Also, the process of migrating and translating content was dicey, and working those issues ate a pile of time out of the schedule. Now, of course, we still have many bugs to fix and features to add. There is graphics work and style sheet clean up to do. Embedded media to implement. Printing issues to solve. Editor bugs to fix. Content to clean. We are far from complete. And we have to get XWiki on a regular upgrade schedule, so we don't let things lag. Fortunately, there is an active XWiki community out there, and we are now part of that effort. It will be good to finally focus on morning forward on new infrastructure, whereas we couldn't go anywhere on the old platform. That's why this was a move, not an upgrade.
Special thanks to the engineering team for pulling this off and to Chris Phelan for leading the entire XWiki phase. Excellent job. We now have a new community development tool to build upon. And the list of community-development tools is growing. Thank you.
Phase 3 of the website transition project very soon.
Friday Oct 23, 2009
By jimgris-Oracle on Oct 23, 2009
The http://opensolaris.org/ website will be unavailable for a period on Monday, October 26th, beginning at 11 a.m. UTC (4 a.m. PDT) as we implement the final migration to XWiki at http://hub.opensolaris.org/. The site will re-open at approximately 10 a.m. PDT.
When the migration is complete, http://opensolaris.org/ and http://www.opensolaris.org/ will redirect to http://hub.opensolaris.org/ (just as they redirect to http://opensolaris.org/os/ right now). Also, a snapshot of the final migrated content will be available for reference at http://stage.opensolaris.org/os/ for 6 months. Editing is not supported on the stage site, though. That site will be maintained only with the final migrated content. This will enable people to check how content was formatted on the old site and manually migrate content that was not part of the automated process during the last 3 months.
Thursday Oct 22, 2009
By jimgris-Oracle on Oct 22, 2009
The opensolaris.org website is not just one place or one
application. It's actually a site of many applications providing a
variety of services to users and developers around the world. Bonnie recently updated the OpenSolaris Site Map to better
organize these services so it's easier to understand
what's out there and how people can use these tools to build
software and community. That last bit is important, too. The more tools
we can provide to enable people to get involved and contribute the more
we can grow as a community. What's cool is that the list is starting to
add up, the number of people maintaining these services is growing, and
more is planned:
- arc.opensolaris.org: Architecture Review Committee case data
- auth.opensolaris.org: Membership/account management application
- bugs.opensolaris.org: Bugs-by-mail submission to Sun's Bugster database
- cr.opensolaris.org: Code review tool
- defect.opensolaris.org: Open defect tracking
- hub.opensolaris.org: XWiki-based site for community editing
- jucr.opensolaris.org: Package/spec file submission
- mail.opensolaris.org: Mailing list management
- pkg.opensolaris.org: Open source package repositories
- pkgfactory.opensolaris.org: Automated collection/build/submission of FOSS to jucr
- poll.opensolaris.org: Community voting
- repo.opensolaris.org: Source code management console: Mercurial & Subversion
- rti.opensolaris.org: Open request-to-integrate tool under development
- src.opensolaris.org: Source browser
- test.opensolaris.org: Access to test farm
Since there are over a dozen
applications making up opensolaris.org, the look and feel varies a bit.
We'll need to solve that as part of the next phase of work in the website transition. We'll layer a more common
graphical feel across everything. After we move off the current portal application on
Monday, we will begin work on Phase 3. We
are planning that work now, and we'll update the infrastructure
to reflect those changes over the next few weeks. I'm looking forward
phase of the project because it will require working with new teams
across the community and all of the
owners of the services above. Once we finish Phase 3 we will have
transitioned the website off of the current infrastructure entirely. We
are doing this in stages, of course, while maintaining current
operations. First was Auth. Then XWiki. And next will be some of the
other key applications that are still currently tied to the old portal.
A note about the list of services above: one application not on the list is the Community Translation Interface.
not on opensolaris.org because it is a tool to facilitate
community translations across all of Sun's FOSS projects, not just
OpenSolaris. This application has enabled many contributions from the
OpenSolaris community, so check it out along with the others.
Tuesday Oct 20, 2009
By jimgris-Oracle on Oct 20, 2009
Well, yesterday Bill implemented our 29th content migration in the last 11 weeks
leading up to the final move to XWiki on hub.opensolaris.org next week.
These migrations over the previous three months have given users
multiple opportunities to check and fix their content and/or file bugs
in preparation for the final move. If all goes well, toward the end of
this week I will announce the final Phase 2 transition details. In the
meantime, please consult these documents if you have questions as you
update your content for migration:
Also, two weeks ago, we notified all users on opensolaris.org about the
upcoming date of 10/26 via individual emails. That was our fourth or
fifth mass email to all users on the site regarding various phases of
the transition. All website transition announcements here.
- Tokyo BarCamp 2010: Photos
- BarCamp Tokyo 2010: 4 Days Away
- Photos: Tokyo Make Meeting 05 2010
- Tokyo OpenSolaris Study Group: May 2010
- Tokyo OpenSolaris Study Group 2010.04
- OpenSolaris Night Seminar 041610
- Tokyo Linux User Group 041610
- Sun Japan
- Tokyo Linux User Group 041010
- OpenSolaris DTrace @ Yokohama Linux UG
No bookmarks in folder
- /Open Source
- /Project Management