concerted-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Atri Sharma <atri.j...@gmail.com>
Subject Re: Website for Concerted
Date Fri, 23 Oct 2015 11:09:29 GMT
Sounds good to me.

On Fri, Oct 23, 2015 at 3:48 PM, Gaurav Shukla <gshukla66@gmail.com> wrote:

> Hi all,
>
> To make posting news and blog items simpler I have followed the scheme
> described below .
>
>  I have added news folder in website repo where all the news related posts
> will be stored in mark down.
> the post name format will be
>
> *YEAR-MONTH-DATE-title_separated_by_underscore.md *
> eg. 2014-10-23-Blogging_with_Butler.md
>
> and permalinks to single post look like
>
> http://localhost:9000/#/pages/news/2014/10/23/Blogging%20with%20Butler
>
> I've also added a pre commit hook which traverses the news folder and
> updates archive.json[1] with new posts in news folder.So in order to post a
> news item one needs to add a markdown file in news folder and commit.
>
> *note: The title should not contain spaces.*
> *         [1] archive.json contains details of all posts in a folder
> grouped by year.*
>
> I will be following the same format for documentation as well as blog
> folders. Is it ok ?
>
> On Thu, Oct 22, 2015 at 6:03 PM, Jake Farrell <jfarrell@apache.org> wrote:
>
> > Tags should be fine then, in my experience projects typically only use
> > tags for releases
> >
> > -Jake
> >
> > On Thu, Oct 22, 2015 at 2:11 AM, Gaurav Shukla <gshukla66@gmail.com>
> > wrote:
> >
> >> Thanks for feedback @Jake. The website is currently displaying tags just
> >> to check the layout and as you and julian pointed out earlier I'll have
> to
> >> make necessary changes in order to display releases that have been voted
> >> and approved.
> >>
> >> So don't worry about that I'll make those changes once the git repo for
> >> concerted is setup and format for release posts have been decided.
> >> On Oct 22, 2015 9:56 AM, "Jake Farrell" <jfarrell@apache.org> wrote:
> >>
> >>> release timeline should contain no release as currently we have not
> voted
> >>> on any release candidates and can not claim to have released anything
> at
> >>> the ASF as of yet
> >>>
> >>> -Jake
> >>>
> >>> On Wed, Oct 21, 2015 at 8:31 PM, Gaurav Shukla <gshukla66@gmail.com>
> >>> wrote:
> >>>
> >>> > I've updated the releases page in website, as of now it is set to
> track
> >>> > calcite repo and  counts tags as releases later this can be changed
> to
> >>> > track releases from  some file with meta data and release notes as
> >>> > suggested by Julian.
> >>> >
> >>> > I've also added team members list (incomplete) on get involved page.
> I
> >>> am
> >>> > displaying name, apache id and role along with github avatar
> >>> >
> >>> > Do I need to display any more details?
> >>> >
> >>> > Updated pages include:
> >>> > http://deathping1994.github.io/concerted-website/#/releases
> >>> > http://deathping1994.github.io/concerted-website/#/contribute
> >>> >
> >>> >
> >>> >
> >>> > On Thu, Oct 22, 2015 at 1:21 AM, Julian Hyde <jhyde@apache.org>
> wrote:
> >>> >
> >>> > > +100
> >>> > >
> >>> > > Making releases is the hardest thing you'll do at apache. Making
> them
> >>> > > reproducible by multiple release managers is even harder.
> >>> > >
> >>> > > On Wed, Oct 21, 2015 at 12:34 PM, Jake Farrell <
> jfarrell@apache.org>
> >>> > > wrote:
> >>> > > > Highly recommend that this process for creating a release
> >>> candidate and
> >>> > > > then promoting it to a release be scripted and heavily documented
> >>> to
> >>> > make
> >>> > > > the process easier and as error free as possible. Here is
a good
> >>> > example
> >>> > > of
> >>> > > > this
> >>> > > >
> >>> > > > release candidate -
> >>> > > > https://github.com/apache/mesos/blob/master/support/vote.sh
> >>> > > > release -
> >>> > https://github.com/apache/mesos/blob/master/support/release.sh
> >>> > > >
> >>> > > > -Jake
> >>> > > >
> >>> > > > On Wed, Oct 21, 2015 at 2:59 PM, Julian Hyde <jhyde@apache.org>
> >>> wrote:
> >>> > > >
> >>> > > >> "Release" is not a git concept. It is a concept that
github
> >>> layers on
> >>> > > >> top of git. The git concepts are branch, commit (with
associated
> >>> sha),
> >>> > > >> tag.
> >>> > > >>
> >>> > > >> I recommend that you apply a git tag to each release
CANDIDATE
> >>> which
> >>> > > >> will become the tag for the release if and when the vote
passes.
> >>> > > >>
> >>> > > >> Each Calcite release has a corresponding news item with
text and
> >>> > > >> metadata. See the metadata at the top of
> >>> > > >>
> >>> > > >>
> >>> > >
> >>> >
> >>>
> https://github.com/apache/incubator-calcite/blob/master/site/_posts/2015-09-02-release-1.4.0-incubating.md
> >>> > > >> .
> >>> > > >> This helps generate the "recent releases" list in
> >>> > > >> http://calcite.incubator.apache.org/news/ and also the
table in
> >>> the
> >>> > > >> downloads page
> >>> > http://calcite.incubator.apache.org/docs/downloads.html.
> >>> > > >>
> >>> > > >> Julian
> >>> > > >>
> >>> > > >>
> >>> > > >> On Wed, Oct 21, 2015 at 10:09 AM, Gaurav Shukla <
> >>> gshukla66@gmail.com>
> >>> > > >> wrote:
> >>> > > >> > Hi, Julian I was looking into a way to fetch releases
from
> >>> github
> >>> > > what I
> >>> > > >> > found was most of the repos in apache don't have
relases they
> >>> have
> >>> > > tags.
> >>> > > >> >
> >>> > > >> > Is this a rule?
> >>> > > >> >
> >>> > > >> > Even calcite does not have releases
> >>> > > >> >
> >>> > > >> >
> https://api.github.com/repos/apache/incubator-calcite/releases
> >>> > > >> >
> >>> > > >> > https://api.github.com/repos/apache/incubator-calcite/tags
> >>> > > >> >
> >>> > > >> > I don't have problem with tags but to fetch date
for those
> tags
> >>> I
> >>> > > have to
> >>> > > >> > find commit url and then find date for that commit.
> >>> > > >> >
> >>> > > >> > Is that how you displayed release date and user
on calcite's
> >>> > website?
> >>> > > >> >
> >>> > > >> > On Wed, Oct 21, 2015 at 10:23 PM, Julian Hyde <
> jhyde@apache.org
> >>> >
> >>> > > wrote:
> >>> > > >> >
> >>> > > >> >>
> >>> > > >> >> > On Oct 20, 2015, at 12:39 AM, Atri Sharma
<
> >>> atri.jiit@gmail.com>
> >>> > > >> wrote:
> >>> > > >> >> >
> >>> > > >> >> > I am fine with fetching contributors and
committers from
> >>> github
> >>> > > >> (mentors,
> >>> > > >> >> > please advice) as long it is clearly mentioned
and
> >>> understandable
> >>> > > on
> >>> > > >> the
> >>> > > >> >> > website.
> >>> > > >> >>
> >>> > > >> >> We did that in Calcite and no one had a problem
with it.
> Every
> >>> > > >> contributor
> >>> > > >> >> has a github account because pull requests are
our preferred
> >>> mode
> >>> > of
> >>> > > >> >> contributions.
> >>> > > >> >>
> >>> > > >> >> In fact this page is generated from that information,
and the
> >>> > > pictures
> >>> > > >> >> come from github:
> >>> > > >> >>
> >>> > > >> >> http://calcite.incubator.apache.org/develop/
> >>> > > >> >>
> >>> > > >> >> The “organization” field was a little more
contentious. Some
> >>> people
> >>> > > feel
> >>> > > >> >> that Apache contributors should leave their
afiliations at
> the
> >>> door
> >>> > > when
> >>> > > >> >> working within Apache. So you should only list
organizations
> if
> >>> > your
> >>> > > >> >> community has broad consensus.
> >>> > > >> >>
> >>> > > >> >> Julian
> >>> > > >> >>
> >>> > > >> >>
> >>> > > >> >> >
> >>> > > >> >> > ASF Git repository is being set up right
now.
> >>> > > >> >> > On 20 Oct 2015 12:51, "Gaurav Shukla" <gshukla66@gmail.com
> >
> >>> > wrote:
> >>> > > >> >> >
> >>> > > >> >> >> By dead link I mean I get 404 project
not found both on
> >>> github
> >>> > > >> mirror as
> >>> > > >> >> >> well as git-wip.apache.org
> >>> > > >> >> >> <
> >>> > https://git-wip-us.apache.org/repos/asf/incubator-concerted.git>
> >>> > > >> >> >>
> >>> > > >> >> >> I'll list PPMC members in html but
current committers and
> >>> > > >> contributors
> >>> > > >> >> can
> >>> > > >> >> >> be fetched directly from github repo
so it will need not
> be
> >>> > > updated
> >>> > > >> >> again
> >>> > > >> >> >> and again.
> >>> > > >> >> >>
> >>> > > >> >> >> Also should I create a blog for this
website using jekyll
> or
> >>> > > should I
> >>> > > >> >> use
> >>> > > >> >> >> the one available in confluence ?
> >>> > > >> >> >>
> >>> > > >> >> >> On Tue, Oct 20, 2015 at 12:44 PM, Atri
Sharma <
> >>> atri@apache.org>
> >>> > > >> wrote:
> >>> > > >> >> >>
> >>> > > >> >> >>> What do you mean by dead link?
> >>> > > >> >> >>>
> >>> > > >> >> >>> It works fine for me.
> >>> > > >> >> >>>
> >>> > > >> >> >>> I like the idea of activity feed.
However we need a hard
> >>> list
> >>> > > >> >> mentioning
> >>> > > >> >> >>> current committers, PPMC members
and contributors.
> >>> > > >> >> >>>
> >>> > > >> >> >>> Also a page for listing newbie
JIRAS.
> >>> > > >> >> >>>
> >>> > > >> >> >>> Let us know if you have any questions.
> >>> > > >> >> >>>
> >>> > > >> >> >>> Regards,
> >>> > > >> >> >>>
> >>> > > >> >> >>> Atri
> >>> > > >> >> >>>
> >>> > > >> >> >>
> >>> > > >> >> >>
> >>> > > >> >> >>
> >>> > > >> >> >> --
> >>> > > >> >> >> Regards !
> >>> > > >> >> >> Gaurav Shukla
> >>> > > >> >> >> gauravshukla.xyz
> >>> > > >> >> >> Phone: +91-837-584-7862
> >>> > > >> >> >>
> >>> > > >> >>
> >>> > > >> >>
> >>> > > >> >
> >>> > > >> >
> >>> > > >> > --
> >>> > > >> > Regards !
> >>> > > >> > Gaurav Shukla
> >>> > > >> > gauravshukla.xyz
> >>> > > >> > Phone: +91-837-584-7862
> >>> > > >>
> >>> > >
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Regards !
> >>> > Gaurav Shukla
> >>> > gauravshukla.xyz
> >>> > Phone: +91-837-584-7862
> >>> >
> >>>
> >>
> >
>
>
> --
> Regards !
> Gaurav Shukla
> gauravshukla.xyz
> Phone: +91-837-584-7862
>



-- 
Regards,

Atri
*l'apprenant*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message