Are we going with the Apache CMS or something else? On Feb 26, 2016 11:10 PM, "David Ash" <[email protected]> wrote:
> Also, depending on how easy the CMS makes it, I'd recommend Bootstrap or a > similar CSS framework that makes design easy, grid-based, and responsive > (for mobile). > > On Fri, Feb 26, 2016 at 10:37 AM, David Ash <[email protected]> wrote: > > > I agree, a CMS is definitely the way to go. What are the CMS options at > > Apache? > > > > On Fri, Feb 26, 2016 at 8:49 AM, Farazath Ahamed <[email protected]> > > wrote: > > > >> i think a CMS would be better in the long run :) > >> On Feb 26, 2016 7:05 AM, "Carlos Perez" < > >> [email protected]> > >> wrote: > >> > >> > I can try to help, but my forte is not really front-end design so it > >> might > >> > end up looking like my old geocities.com site (tables everywhere, who > >> > needs divs). =o) > >> > > >> > In either case, I will give it a shot… I just need a pointer, should I > >> > work in pure html or is the CMS the way to go? > >> > > >> > Carlos > >> > > >> > On 2/25/16, 9:08 AM, "DRAGOSH, PAMELA L (PAM)" < > >> [email protected]> > >> > wrote: > >> > > >> > >The CMS has not been done, I only put a index.html up to test that > the > >> new > >> > >git site works in the Apache infrastructure to properly show the page > >> to > >> > >the internet. > >> > > > >> > >Can someone please help with setting that up? I’m going to focus on > the > >> > >JIRA issues today and pulling in David’s code. > >> > > > >> > >Thanks!! > >> > > > >> > >Pam > >> > > > >> > >On 2/25/16, 7:57 AM, "Carlos Perez" < > [email protected] > >> > > >> > >wrote: > >> > > > >> > >>Hi everyone, I apologize for the sudden disappearing act but I got > >> caught > >> > >>up in work for a while and the had a long overdue vacation. Did we > get > >> > >>the CMS up and running for the project, is that where we are hosting > >> the > >> > >>site content, or are we doing this all through the index.html page I > >> saw > >> > >>uploaded recently? > >> > >> > >> > >>Let me know, > >> > >> > >> > >>Carlos > >> > >> > >> > >>Sent from Nine<http://www.9folders.com/> > >> > >> > >> > >>From: David Ash <[email protected]> > >> > >>Sent: Feb 24, 2016 7:07 PM > >> > >>To: dev > >> > >>Subject: Re: Next steps > >> > >> > >> > >>Oh, without the last bit - forgot to delete the leftover draft bits > >> > >>before > >> > >>sending ;-) > >> > >> > >> > >>(So ignore this part: > >> > >> > >> > >>I. What is Apache OpenAZ? > >> > >> - Should not be wordy > >> > >> > >> > >>I. Documentation > >> > >> > >> > >>) > >> > >> > >> > >>On Wed, Feb 24, 2016 at 5:04 PM, David Ash <[email protected]> > >> wrote: > >> > >> > >> > >>> Here's my 2 cents for a quick draft of a structure for a website: > >> > >>> > >> > >>> I. Homepage > >> > >>> - What is Apache OpenAZ? (very briefly, marketing material) > >> > >>> - Release information > >> > >>> - Links > >> > >>> > >> > >>> II. General information > >> > >>> - About (maybe more detailed) > >> > >>> - License > >> > >>> - FAQ > >> > >>> > >> > >>> III. Download > >> > >>> > >> > >>> IV. Documentation > >> > >>> - Quick start guide > >> > >>> - Detailed documentation > >> > >>> - Wiki > >> > >>> > >> > >>> V. Support > >> > >>> > >> > >>> VI. Community > >> > >>> - Mailing lists > >> > >>> - Bug reports > >> > >>> - Developer information > >> > >>> - Contributors > >> > >>> - Sponsors / Sponsorships > >> > >>> > >> > >>> > >> > >>> > >> > >>> > >> > >>> I. What is Apache OpenAZ? > >> > >>> - Should not be wordy > >> > >>> > >> > >>> I. Documentation > >> > >>> > >> > >>> On Wed, Feb 24, 2016 at 7:13 AM, DRAGOSH, PAMELA L (PAM) < > >> > >>> [email protected]> wrote: > >> > >>> > >> > >>>> Colm, thanks. > >> > >>>> > >> > >>>> A) I¹m a little tied up and need some help. If someone could just > >> help > >> > >>>>get > >> > >>>> the structure of it, I¹ll be happy to then add in content. > >> > >>>> > >> > >>>> B & C) I will try to get this done. > >> > >>>> > >> > >>>> Thanks! > >> > >>>> > >> > >>>> Pam > >> > >>>> > >> > >>>> On 2/24/16, 8:48 AM, "Colm O hEigeartaigh" <[email protected]> > >> > >>>>wrote: > >> > >>>> > >> > >>>> >Hi all, > >> > >>>> > > >> > >>>> >It's good that we had a fruitful discussion on the previous > mail I > >> > >>>>sent > >> > >>>> >surrounding the project. It's clear that there is at least some > >> > >>>>interest > >> > >>>> >in > >> > >>>> >the project, and it makes sense to try to promote it a little > >> more. > >> > >>>> >However, I remain a bit sceptical, as really for a project to > >> succeed > >> > >>>>in > >> > >>>> >the incubator IMO, it needs the people who submit it to drive > >> initial > >> > >>>> >interest in it. > >> > >>>> > > >> > >>>> >Here are some next steps to take > >> > >>>> > > >> > >>>> >a) Website. We badly need to get a website up and running. > >> > >>>> > > >> > >>>> >b) Pull requests. Can Pam or someone more familiar with OpenAz > >> than I > >> > >>>> take > >> > >>>> >a look at the outstanding pull requests? > >> > >>>> > > >> > >>>> >https://github.com/apache/incubator-openaz/pulls > >> > >>>> > > >> > >>>> >To apply them, simply click on each pull request to get the URL. > >> What > >> > >>>>I > >> > >>>> >normally do is download the patch using "wget" and appending > >> ".patch" > >> > >>>>to > >> > >>>> >the URL, and then apply it locally via "git am <file>": e.g.: > >> > >>>> > > >> > >>>> > > >> > >>>> > >> > >>>> > >> > > https://patch-diff.githubusercontent.com/raw/apache/incubator-openaz/pu > >> > >>>>l > >> > >>>>l/ > >> > >>>> >3.patch > >> > >>>> > > >> > >>>> >If the patches are good, you have to edit the commit message to > >> say > >> > >>>>"This > >> > >>>> >closes #3" to close that particular pull request. > >> > >>>> > > >> > >>>> >c) Do a quick JIRA triage beyond the pull requests, and see what > >> > >>>>makes > >> > >>>> >sense to include in an initial release. > >> > >>>> > > >> > >>>> >Once a - c are done, we can think about getting a release out. > >> > >>>> > > >> > >>>> >Colm. > >> > >>>> > > >> > >>>> > > >> > >>>> >-- > >> > >>>> >Colm O hEigeartaigh > >> > >>>> > > >> > >>>> >Talend Community Coder > >> > >>>> >http://coders.talend.com > >> > >>>> > >> > >>>> > >> > >>> > >> > >> > >> > >>This e-mail message and any attachments to it are intended only for > >> the > >> > >>named recipients and may contain legally privileged and/or > >> confidential > >> > >>information. If you are not one of the intended recipients, do not > >> > >>duplicate or forward this e-mail message. > >> > > > >> > > >> > > >> > This e-mail message and any attachments to it are intended only for > the > >> > named recipients and may contain legally privileged and/or > confidential > >> > information. If you are not one of the intended recipients, do not > >> > duplicate or forward this e-mail message. > >> > > >> > > > > >
