( note - Moved this to aeolus-comm-mgmt(a)lists.fedorahosted.org.
On 13/11/2012, at 7:29 PM, Giulio Fidente wrote:
> hi there,
> given that each cabal should have its first meeting by the end of this
> week, my proposal for the first meeting of the release cabal is for
> Thursday the 15th, at 18:00 CET (which is GMT+1)
NACK. Steve already set up a first meeting time, at 15:00 CET on
Friday. I'll forward the invite to you. :)
> I'd like to use for this and the next meetings IRC, as it happens for
> fedora, I'm thinking of a channel called: '#aeolus-meeting'
Good idea. I'm fairly certain this already happens occasionally, but
it's a decent idea to make it part of the standard approach.
> We should book such a channel on a shared calendar which will eventually
> be published on the website to encourage people join us.
Very good idea. :)
> My proposals for the agenda (and please feel free to add other stuff
> which you think is important):
> * wrap up on the current status of art
> * review the existing install docs and look for improvements
> * define some 'recurring' date for our next meetings
Good thinking. Just created a page on our Etherpad with meeting info,
agenda items, and similar:
> Note that today we've got a guy on #aeolus asking, amongst other things,
> if there guides helping to install aeolus on centos.
> Having aeolus working on centos looks to me a nice task as that is
> probably going to be the preferred choice for non-paying (yet) customers.
Agreed. My preference would be to have Aeolus working on CentOS 6.x as
our "primary" target platform. It's what most upstream rpm users will
likely want to use, and (unlike Fedora) we don't have to jump through
hoops every few months trying to make it work with a new release that
has significant changes. :)
Regards and best wishes,
>  https://fedoraproject.org/wiki/Meeting_channel?rd=Fedora_meeting_channel
> Giulio Fidente, gpg key id 08D733BA
> Giulio Fidente
Aeolus Cloud Evangelist
- Matt Wagner elected as Awesome
- Agreed to Thursday, 14:30 GMT as permanent meeting time
- Will meet on Tuesday next week, due to Thanksgiving
- We will use github issues for tracking items
- Matt will enter initial items
- any unclaimed items will be discussed during the next meeting
- Website Cabal will help maintain etherpad and other communal web-based resources
- make sure that this information is documented and organized
- Matt will send out this information
- Blog posts - is getting people to write them the responsibility of Website or Publicity Cabal?
- Open question for now, will be brought up at the Publicity Cabal
- News and Blog
- Using blog for news makes sense
- Also want changelog for product version changes
- Release notes
- aggregate git commits, or commit statistics
- Wiki is currently Conductor only
- wikis are moving to github
- maybe eventually make website wiki page a static page with links to project wikis
- Need to increase visibility of other projects, not just Conductor
- Github issue will be created to track this
- Andy and Dan to work on initial proposal for website changes to support this
- Should we use aeolus incubator as staging version of website?
- can just fork github and use github pages
- Mo's patchset discussion
- request to break it up into individual patches
- revised project page seems fine, also replaces About page
- combining get it/use it into install makes sense
- other items require further discussion
On 13.11.2012 17:00, Matt Wagner wrote:
>> * Projects - the thing that Mo has done. We have so many components now that people deserve a special page just to get the 3048 meter (ten thousand foot) view of Aeolus.
> has some overlap too, I think, though it's more about what currently
>> * Install - describe how to download and install Aeolus. "Get It" is fine too, but I just think "Install" is clearer and more common. Regarding content of the page, we should decouple it from Fedora, as discussed on the Conference.
> Does this entail squashing 'Get It' and 'Use It' into one section?
It's more like renaming 'Get It' to 'Install' and putting there instructions for also other systems than Fedora. And 'Use It' in my opinion should get away in favor of Docs page, and on the Docs page the first link can be 'Tutorial', which would be what we now call 'Use It'. Docs page would also contain other links. See below.
>> * Docs - point of origin when you search for tutorials, reference guides etc., regardless of who you are. Link to our usage guide with screenshots, links to GitHub wikis (when we have them) of various subprojects, links to API docs. We should make clear what links are for what "persona". I'd differentiate here between three groups: Admins (Sam, the sys admin - installation and setup), Users (Dennis, the app designer + Carl/Bert, the infrastructure consumer - clicking and CLIing), Developers. -- Yeah, Mike, the develper persona might be useful :)
> This makes a lot of sense to me. Though I'm not sure how to present the
> personae information in a way that will be clear to new users, who
> probably won't think of themselves as "Connor the Infrastructure
> Consumer" or whatnot.
I could see 3 subheadings on the Docs page.
* For Admins (related to aeolus-configure and similar)
* For Users (related to Conductor WUI and CLI mostly)
* For Developers (related to API mostly)
I wouldn't squeeze much info here, the Docs page should not be much more than a set of links to proper documentation (documentation itself can be on the website or GH wikis or both).
>> * Contribute - information for everyone who wants to help. What stuff we need - helping newbies, updating tutorials, writing code etc. and how should people get involved (installation for development, finding easy "onboarding" stuff to work on, etc.).
> We have really bad docs here right now, I think. So this could be good.
> That said -- how many people are actually trying to contribute right
IMO that's a chicken and egg problem. There can't be many people trying to contribute if we don't give them any info. Currently, the aeolusproject.org site doesn't look like we want/appreciate contributions. I'd like to change that.
A thing worth noting - I don't consider just pull requests as contributions, it could be also helping newbies on #aeolus so that we don't have to do it, it could be packaging for Debian or whatever. But again, I think we can't expect people to do that unless we actually tell them that we'd like them to do that. I'd like to bring this up on the next Website Cabal and take creating the "Contribute" page as my responsibility, if we agree that we want to have it.
>> * Blog - feed from our external blog. (Or, we could move the blog to be part of the website. Not sure if there would be issues with this though.) We could get rid of News section, as Mo did in his pull request. I think Blog/News are largely overlapping and we might struggle to find enough items for News section alone. Or, should News stay, I'd let them be only on the Home page with some link to show older news, but I wouldn't put that into main menu. I believe this main menu item wouldn't be used much.
> Can we just make this a link to blog.aeolusproject.org? That would, by
> far, be the easiest choice.
>> * Contact / Need help? / something else? - not sure of the name here, but the purpose of the page is the same as we have it now - document our communication channels, allow people to reach out for help or give feedback.
> Agreed, though I'd like to give the Contact page some TLC since right
> now I think it's kind of overwhelming. (IMHO).
> What about the News tab? Does that just fall under the Blog and/or get
> duped on the homepage?
The blog/news issue has been solved on the Cabal, others please see:
You were very active with the outreach for GSOC, and
that had a pretty decent result. :)
Would you be interested in doing another, similar
Mfojtik mentioned on IRC that Deltacloud is already
involved, and they already have 2 applications.
Seems like it might be a good opportunity for us.
Your kind of thing?
Regards and best wishes,
Aeolus Cloud Evangelist
On 13/11/2012, at 6:19 PM, Justin Clift wrote:
Oops, bad cut-n-paste. That should be:
Aeolus Cloud Evangelist