Re: Migrating Community from Github and GoggleGroups to Apache

[Lewis John Mcgibbney]

Hi Matt,

On Sat, Mar 26, 2016 at 9:47 AM, Matt Post  wrote:

> What is the new codebase convention supposed to be?


So now, the canonical Joshua codebase MUST be at [0]
The Github mirror at [2] is merely a mirror NOT the canonical source. All
of the future releases of Joshua will be cut from the source at [0] meaning
that all code development must now be transitioned to that codebase.

[0] https://git-wip-us.apache.org/repos/asf/incubator-joshua.git



> Does development still happen at [1] and get mirrored to [2]
> automatically?


No, essentially [1] gets shut down with a notice (apache branch README)
telling people that the canonical source is at [0] however there is a
convenient mirror at [2] for pull requests, etc. The notice should also say
that the new website is at http://joshua.incubator.apacha.org


> I am uncertain what I am supposed to do (i.e., where I should set origin
> to be on my personal checkouts).
>

So origin is now [0]


>
> [1] https://github.com/joshua-decoder/joshua
> [2] https://github.com/apache/incubator-joshua
>
> I have created the apache branch on the main repo and pushed it up.


Great, can you make this the default branch on the repository so that when
people try to navigate there the README clearly directs them towards [0]
for the canonical source or [2] for the mirror?

I notice that [1] and [0] are out of sync now actually. Would it be
possible for you to forward port all of the code augmentations which have
taken place since following commit

mjpost  Added ability to add, remove, and list
rules in the private phrase table


to [0]?
Once this is done, I would suggest that you make [1] read only as this will
prevent the codebases diverging again.
Thanks, this is not typically a painful process however once in place we
will be good to go and begin building the community out.

Re: Migrating Community from Github and GoggleGroups to Apache

[Lewis John Mcgibbney]

Hi Matt,

On Sat, Mar 26, 2016 at 9:38 AM, Matt Post  wrote:

>
> What are the framework options?


For building the website documentation...essentially anything we want. The
blocker was the mechanism by which we would publish the website not how we
build the website documentation.
Over on https://issues.apache.org/jira/browse/INFRA-11295 it looks like we
obtained a reasonable degree of consensus on Gitpubsub, as explained in
https://blogs.apache.org/infra/entry/git_based_websites_available, if you
are happy with this then we can address the Website this weekend... or at
least PING Infra again with the aim of getting us set up with Gitpubsub.


> I was hoping that we could take advantage of the move to improve Joshua's
> website, which is really quite ugly. Is there any help available for this?
> Are there common Apache themes or something we could use? I currently have
> Jekyll underneath, so it wouldn't be that hard to swap out some templates.


In terms of help... no not really in all honesty. It is down to us to get a
Website together. I am pretty cool with Jekyll it seems good to me. If we
can get or develop a better template then I am all for that.


> Jekyll is nice because you can write in Markdown and then convert, but I
> am open to other ideas if there's something newer and nicer. I would love
> to move to something wiki-like that permits web-based editing, instead of
> pushing and pulling with git.
>

Mm. OK then, so it looks like Gitpubsub is not what you are a looking
for. If you are looking for the CMS-based backing for the website then we
could opt for the Apache CMS http://www.apache.org/dev/cms.html

If you want to go for the CMS then let us know and we can get this going.
This is the main blocker for us getting a website going.


>
> We could just start by seeding the current website, but I am a little
> afraid that decreases the chances we'll do something new.
>
>
Yes and no. I mean it is best f we have something at
http://johsua.incubator.apache.org right? Someone/people would then merely
have to make a point of upgrading/updating/overhauling the website. This
could easily be tracked in Jira.

wdyt?
Lewis



-- 
*Lewis*

Re: Migrating Community from Github and GoggleGroups to Apache

[Matt Post]

Lewis,

What are the framework options? I was hoping that we could take advantage of 
the move to improve Joshua's website, which is really quite ugly. Is there any 
help available for this? Are there common Apache themes or something we could 
use? I currently have Jekyll underneath, so it wouldn't be that hard to swap 
out some templates. Jekyll is nice because you can write in Markdown and then 
convert, but I am open to other ideas if there's something newer and nicer. I 
would love to move to something wiki-like that permits web-based editing, 
instead of pushing and pulling with git.

We could just start by seeding the current website, but I am a little afraid 
that decreases the chances we'll do something new.

matt


> On Mar 25, 2016, at 3:22 PM, Lewis John Mcgibbney  
> wrote:
> 
> The only concern I have is if the codebases now diverge. That is a very
> real possibility Nd I've seen it happen time and time again.
> 
> We are essentially waiting in absolutely nothing to get the website
> running, all we are waiting on is deciding on a framework, etc.
> 
> If you guys want I can just clone and launch the existing website over on
> joshua.incubator.apache.org (so that something is there), we could then do
> the other tasks over the weekend.
> Any thoughts on that?
> 
> On Friday, March 25, 2016, Matt Post  wrote:
> 
>> Lewis -- regarding your requests 1--3, I've been waiting until we had
>> versions of everything migrated before announcing the move (you asked me a
>> long time ago to make announcements). What do we need to do before the new
>> website is live? It seems worthwhile to have that running before pointing
>> people at it.
>> 
>> matt
>> 
>> 
>>> On Mar 25, 2016, at 2:22 PM, Lewis John Mcgibbney <
>> lewis.mcgibb...@gmail.com > wrote:
>>> 
>>> BOOM
>>> 
>>> https://github.com/apache/incubator-joshua
>>> 
>>> 
>>> 
>>> On Thu, Mar 24, 2016 at 10:55 AM, Lewis John Mcgibbney <
>>> lewis.mcgibb...@gmail.com > wrote:
>>> 
 Thanks Matt, enjoy the time off (hopefully you are not ill)
 Later
 
 On Thu, Mar 24, 2016 at 10:54 AM, Matt Post > > wrote:
 
> (offline yesterday and today, will do tomorrow)
> 
> matt (from my phone)
> 
>> On Mar 24, 2016, at 1:48 PM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com > wrote:
>> 
>> Hi Matt,
>> As the primary figure within the Joshua community I wonder if you can
> act
>> on the following. It will go a long way in enabling us to transition
> things
>> over.
>> 
>> 1. Can you create a new branch on the Github repos at [0] called
>> 'apache' with only a README which states that the Joshua project has
> been
>> transitioned to the Apache Incubator. A link to the Github repos at
> [1]
>> (I've opened [2] to get this set up) would be great. Also a link to
> the new
>> website (once we get it up and running) at [3].
>> 2. Post a message to the existing Joshua Google Groups which states
> that
>> same as the above however references the new mailing lists at
>> u...@joshua.incubator.apache.org  and
>> dev@joshua.incubator.apache.org 
>> 3. Post to the Joshua Website that the project has been migrated over
> to
>> the Apache Software Foundation and provide relevant links as posted
> above.
>> 
>> If we address the above it would be ideal.
>> 
>> Thanks Matt, please let me know if there are any clarifications
> required.
>> 
>> [0] https://github.com/joshua-decoder/joshua
>> 
>> [1] http://github.com/apache/incubator-joshua
>> 
>> [2] https://issues.apache.org/jira/browse/INFRA-11539
>> 
>> [3] http://joshua.incubator.apache.org
>> 
>> --
>> *Lewis*
> 
> 
 
 
 --
 *Lewis*
 
>>> 
>>> 
>>> 
>>> --
>>> *Lewis*
>> 
>> 
> 
> -- 
> *Lewis*