Website template (was Re: Anyone working...)

[Pierre Smits <pi...@gmail.com>]

Venkat,

May I suggest that you fill your iCLA with the secretary of the ASF
(regarding licensing issues) and have your details added to the list.

I also advice you to open up a JIRA issue regarding this, so that
screenshots etc can be uploaded as starting points for discussions. The ASF
ml system doesn't forward attachments (screenshots, etc) to a ml.

Best regards,

Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Fri, Jul 10, 2015 at 6:53 PM, Venkat Muthuswamy <
venkat.muthuswamy@esgyn.com> wrote:

> Dave,
>
> I will work with you on this. I'll create a website template and we can
> review and extend it.
> And in the mean time we can figure out the logistics to get it integrated.
>
> thanks
> Venkat
>
> On Fri, Jul 10, 2015 at 9:31 AM, Dave Birdsall <da...@esgyn.com>
> wrote:
>
> > Hi,
> >
> > At the moment I don't think anyone is working on it. Alice Chen was doing
> > most of the work there but was redirected, so some regrouping is needed.
> >
> > To get that thought process going, I'll think out loud a bit, a mixture
> of
> > statements and questions. Comments welcome.
> >
> > Before we went Apache, we had a single web site, www.trafodion.org
> (still
> > out there). That had a variety of content, broken down into the following
> > areas:
> >
> > 1. Understanding the software -- contained a description of Trafodion's
> > architecture (in some detail), lists of recently released features, and
> > roadmaps
> > 2. Using the software -- contained information about download and
> > installation (including a pointer to a downloads page), and high level
> > description of how to use the software (e.g., how to start a Trafodion
> > instance)
> > 3. Contributing -- detailed descriptions of the mechanics of contributing
> > to Trafodion (this has been updated with Apache practices, so it is
> > current)
> > 4. Community -- description of governance, and lists of people who were
> > currently working on Trafodion and their areas of specialization, and
> > community events
> > 5. Documentation -- the SQL manual and related documentation
> > 6. Other stuff, e.g. videos and an FAQ
> >
> > In the Apache world, Trafodion itself is on a course to have two web
> sites:
> > http://trafodion.incubator.apache.org/ and a wiki,
> >
> https://cwiki.apache.org/confluence/display/TRAFODION/Apache+Trafodion+home
> > .
> > First question that pops into my mind is, how should content be broken
> down
> > between the two?
> >
> > Alice's idea for http://trafodion.incubator.apache.org/ was for it to be
> > built as part of the daily build from the source repository. One benefit
> of
> > that is that the workflow for changing the web site was identical to that
> > for changing Trafodion code itself. It would be subject to the same
> review
> > standards and go through continuous integration. Updating the wiki of
> > course uses a different workflow and has a different permissions
> structure.
> >
> > And of course some of the material on www.trafodion.org will no longer
> be
> > relevant in the Apache world so it goes away, or is replaced with
> pointers
> > to general Apache web sites.
> >
> > The current state of things seems to be:
> >
> > 1. Understanding the software -- none of this is on Apache yet; the stuff
> > on the old wiki is up-to-date
> > 2. Using the software -- none of this is on Apache yet; the stuff on the
> > old wiki is up-to-date
> > 3. Contributing -- general high level info + a list of current
> contributors
> > is present on the Apache wiki (
> >
> https://cwiki.apache.org/confluence/display/TRAFODION/Apache+Trafodion+home
> > ),
> > while detailed instructions about navigating Trafodion development
> > infrastructure (git, Jenkins and the like) are up to date on the old wiki
> > www.trafodion.org.
> > 4. Community -- future events has a page on the Apache wiki; past events
> > are on the old wiki. Governance material on the old wiki is obsolete as
> it
> > is pre-Apache.
> > 5. Documentation -- none of this is on Apache yet; the manuals are
> > up-to-date with respect to the last release of Trafodion but do not
> contain
> > new features developed since (which is an additional concern)
> > 6. Other stuff -- none of this is on Apache yet
> >
> > Looking at this list: Governance stuff should go away, replaced by
> pointers
> > to the appropriate ASF pages. As to the rest...
> >
> > Getting back to the question of which site should hold what content: I'd
> > like to suggest that technical content (documentation, architectural
> > description, and the like) should be on the
> > http://trafodion.incubator.apache.org/ web site, and go through the same
> > workflow as code does.Information about contributing and community, along
> > with "other stuff" seems like appropriate content for the wiki. My
> > rationale is that the technical content should reflect the code and
> > therefore be in sync with it. What do others think?
> >
> > A procedural question: Once we get consensus on what goes where, the next
> > step seems to be to structure a work program around it. Are JIRAs the
> right
> > mechanism to do this? A JIRA sounds right for the stuff that goes through
> > normal workflow. Would it be appropriate to use a JIRA for the wiki site
> as
> > well?
> >
> > Welcoming thoughts and further discussion,
> >
> > Dave
> >
> >
> >
> > On Fri, Jul 10, 2015 at 8:14 AM, Stack <st...@duboce.net> wrote:
> >
> > > Anyone working on the website? This don't look too good as home page:
> > > http://trafodion.incubator.apache.org/
> > >
> > > Yours,
> > > St.Ack
> > >
> > > On Mon, Jun 29, 2015 at 3:20 PM, Stack <st...@duboce.net> wrote:
> > >
> > > > I updated our status page
> > > > http://incubator.apache.org/projects/trafodion.html
> > > >
> > > > Anyone on the website?
> > > >
> > > > We going to make a new logo with Apache in it?
> > > >
> > > > St.Ack
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>