trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alice C." <alc...@apache.org>
Subject Re: Anyone working on putting up a website at trafodion.incubator.apache.org and....
Date Tue, 14 Jul 2015 23:24:38 GMT
Cool! Thanks for looking into it Steve!

Cheers,
Alice

> On Jul 14, 2015, at 4:18 PM, Steve Varnau <steve.varnau@esgyn.com> wrote:
> 
> Goeffrey in INFRA team poked it and it is published now!
> 
> On Tue, Jul 14, 2015 at 3:41 PM, Steve Varnau <steve.varnau@esgyn.com>
> wrote:
> 
>> I sure don't see anything missing.
>> You pushed the content to:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion-site.git;a=tree;h=refs/heads/asf-site;hb=refs/heads/asf-site
>> 
>> And the repo is set up for gitwcsub according to:
>> https://issues.apache.org/jira/browse/INFRA-9831
>> 
>> According to INFRA blog, that should be all that is needed:
>> https://blogs.apache.org/infra/entry/git_based_websites_available
>> 
>> I'll post a question in the JIRA.
>> 
>> -Steve
>> 
>>> On Sun, Jul 12, 2015 at 11:30 PM, Alice Chen <alchen@apache.org> wrote:
>>> 
>>> I've committed the code for Maven to generate the site to the
>>> incubator-trafodion repository.  I've also committed the static site
>>> generated by Maven to incubator-trafodion-site repository asf-site branch.
>>> It doesn't seem like gitpubsub is picking up the commit.  Is there
>>> something else we need to do to trigger an update?
>>> 
>>> Cheers,
>>> Alice
>>> 
>>> On Fri, Jul 10, 2015 at 4:52 PM, Dave Birdsall <dave.birdsall@esgyn.com>
>>> wrote:
>>> 
>>>> Thank you, Alice!
>>>> 
>>>>> On Fri, Jul 10, 2015 at 4:43 PM, Alice Chen <alchen@apache.org>
wrote:
>>>>> 
>>>>> I've created the following JIRA
>>>>> https://issues.apache.org/jira/browse/TRAFODION-31 to track the
>>> website
>>>>> and
>>>>> have assigned it to myself (I'm a JIRA admin).
>>>>> 
>>>>> Cheers,
>>>>> Alice
>>>>> 
>>>>> On Fri, Jul 10, 2015 at 3:21 PM, Dave Birdsall <
>>> dave.birdsall@esgyn.com>
>>>>> wrote:
>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> Perhaps the next step then is creating a JIRA and checking in this
>>> work
>>>>>> under it? Alice, do you want to create the JIRA? If you'll send me
>>> your
>>>>>> JIRA ID I can add you as a contributor so you can assign it to
>>>> yourself.
>>>>>> 
>>>>>> Dave
>>>>>> 
>>>>>>> On Fri, Jul 10, 2015 at 3:17 PM, Stack <stack@duboce.net>
wrote:
>>>>>>> 
>>>>>>> On Fri, Jul 10, 2015 at 3:12 PM, Alice C. <alchen@apache.org>
>>> wrote:
>>>>>>> 
>>>>>>>> The color scheme can be changed if we want to use another
color
>>>>> scheme.
>>>>>>> Site looks great. I'd suggest putting up what you have and then
>>>> taking
>>>>> it
>>>>>>> from there... improving piecemeal.
>>>>>>> 
>>>>>>> St.Ack
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> Cheers,
>>>>>>>> Alice
>>>>>>>> 
>>>>>>>>> On Jul 10, 2015, at 2:57 PM, Pierre Smits <
>>>> pierre.smits@gmail.com>
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> HI Alice,
>>>>>>>>> 
>>>>>>>>> Looks indeed very tight/sharp. What I don't like is the
>>> umpteen
>>>>>> shades
>>>>>>> of
>>>>>>>>> grey or gray (but that is just me and my prefs).
>>>>>>>>> 
>>>>>>>>> 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 11:22 PM, Alice C. <
>>> alchen@apache.org>
>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>> Hello,
>>>>>>>>>> 
>>>>>>>>>> I've generated a basic site for Trafodion using Maven
with
>>> the
>>>>>> Fluidio
>>>>>>>>>> skin and AsciiDoc.  Please check it out at
>>>>>>>>>> http://people.apache.org/~alchen/trafodion/ . Let
me know if
>>>>> this a
>>>>>>>> good
>>>>>>>>>> starting point for the website and I'll commit what
I have.
>>>>>>>>>> 
>>>>>>>>>> Cheers,
>>>>>>>>>> Alice
>>>>>>>>>> 
>>>>>>>>>>>> On Jul 10, 2015, at 11:34 AM, Carol Pearson
<
>>>>>>>> carol.pearson234@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Hi,
>>>>>>>>>>> 
>>>>>>>>>>> I've spent some time looking at the Apache wiki
and looking
>>> at
>>>>> what
>>>>>>>> other
>>>>>>>>>>> Apache projects have as their wikis as well,
and the
>>>> distinction
>>>>>>>> between
>>>>>>>>>>> those and the project websites, then doing what
Dave did
>>> above
>>>> -
>>>>>>> asking
>>>>>>>>>>> what information needs to go at which location,
how do we go
>>>>> about
>>>>>>> the
>>>>>>>>>>> separation etc.
>>>>>>>>>>> 
>>>>>>>>>>> It seems to me that the distinctions on content
on the
>>> various
>>>>>> Apache
>>>>>>>>>> wikis
>>>>>>>>>>> versus websites is pretty clear. The wikis are
mostly
>>> oriented
>>>>>>> toward a
>>>>>>>>>>> brief product introduction  (Pierre, I saw your
comment on
>>> the
>>>>>>> current
>>>>>>>>>> wiki
>>>>>>>>>>> that what we have there now really belongs on
the website -
>>>> were
>>>>>> you
>>>>>>>>>>> suggesting that we have a 2-3 sentence intro
and a pointer
>>> to
>>>> the
>>>>>>>> website
>>>>>>>>>>> on the wiki front page?)  and then quickly into
the welcomes
>>>> and
>>>>>>>> how-tos
>>>>>>>>>>> for contributing.
>>>>>>>>>>> 
>>>>>>>>>>> Some Apache wikis have more information about
the product as
>>>>> well,
>>>>>>> but
>>>>>>>>>>> others put that entirely on their websites. 
For example the
>>>>> Ambari
>>>>>>>> wiki
>>>>>>>>>>> has quick start for setting up Ambari, troubleshooting,
>>> etc.,
>>>>> which
>>>>>>> is
>>>>>>>>>> not
>>>>>>>>>>> strictly developer/contributor oriented, and
info about
>>>> features
>>>>>> that
>>>>>>>> are
>>>>>>>>>>> not yet part of the project, for example.  The
Qpid Wiki is
>>>> very
>>>>>>>> sparse.
>>>>>>>>>>> Bigtop is pretty active and shows a balance focused
mostly
>>> on
>>>>>>> mechanics
>>>>>>>>>> and
>>>>>>>>>>> development while the website shows a broader,
more
>>>> informational
>>>>>>>> focus.
>>>>>>>>>>> Not quite the same domain but maybe that's an
illustrative
>>>> model?
>>>>>>>>>>> 
>>>>>>>>>>> I note that in the list of Spaces, there is no
description
>>> for
>>>>>> Apache
>>>>>>>>>>> Trafodion, so we should add that. I also note
some
>>>>> inconsistencies,
>>>>>>>> where
>>>>>>>>>>> some things have Apache in front of them and
some don't,
>>> making
>>>>> it
>>>>>>>> harder
>>>>>>>>>>> to search alphabetically - I couldn't find Qpid,
for
>>> example,
>>>>>> until I
>>>>>>>>>>> looked under Apache Qpid.
>>>>>>>>>>> 
>>>>>>>>>>> On the mechanics of website building, I think
it's a good
>>> idea
>>>> to
>>>>>>> have
>>>>>>>> it
>>>>>>>>>>> under control and built regularly.  That allows
fallback to
>>>>>> previous
>>>>>>>>>>> versions, etc., which can be a problem for websites,
and as
>>> we
>>>>>> extend
>>>>>>>>>> with
>>>>>>>>>>> different releases, we have the appropriate website
>>> versions as
>>>>>> well.
>>>>>>>>>> But
>>>>>>>>>>> it also adds a burden on our current set of committers
>>> because
>>>>>> those
>>>>>>>> are
>>>>>>>>>>> additional changes that need to be approved.
>>>>>>>>>>> 
>>>>>>>>>>> -Carol P.
>>>>>>>>>>> 
>>>>>>>>>>> On Fri, Jul 10, 2015 at 11:09 AM, Pierre Smits
<
>>>>>>> pierre.smits@gmail.com
>>>>>>>>> 
>>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> May I suggest the following as a starting
point:
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 1. Have marketing and promotional pages (the
more static
>>>> ones)
>>>>> in
>>>>>>> the
>>>>>>>>>>>> website, this means for the product  the
description,
>>>>>> documentation
>>>>>>>> re
>>>>>>>>>>>> latest available release, intended use etc,
and for the
>>>> project
>>>>>>>>>>>> high-level
>>>>>>>>>>>> outlines and references to wiki pages
>>>>>>>>>>>> 2. Have community internal and other frequently
changed
>>> pages
>>>>> in
>>>>>>> the
>>>>>>>>>>>> wiki, but also release notes (copy-paste
from JIRA), etc.
>>>>>>>>>>>> 
>>>>>>>>>>>> I find JIRA issues a good thing to track
assignment and
>>>>> progress,
>>>>>>> even
>>>>>>>>>> for
>>>>>>>>>>>> websites. Just mentioning stuff in a mailing
list could
>>> lead
>>>> to
>>>>>>>>>>>> forgotten/not done, due to the high pace
of overcrowding.
>>>>>>>>>>>> 
>>>>>>>>>>>> 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:31 PM, Dave Birdsall
<
>>>>>>>> dave.birdsall@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 <stack@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 <
>>> stack@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
>> 
>> 
>> 
>> --
>> -Steve
> 
> 
> 
> -- 
> -Steve

Mime
View raw message