On Thu, May 28, 2015 at 05:28:15PM +0200, Emmanuel Bernard wrote:
>
> > On 28 May 2015, at 16:06, Steve Ebersole wrote:
> >
> > The "next gen blog" has been "coming" for years. That's not a dig at
> > anyone, just a simple point that I'd rather plan based on options I have
> > today rather th
So even though GitHub does not support RSS per-se, it does have a lot of
JSON support, including around these releases, including even creating them!
On Thu, May 28, 2015 at 10:28 AM, Emmanuel Bernard
wrote:
>
> On 28 May 2015, at 16:06, Steve Ebersole wrote:
>
> The "next gen blog" has been "c
> On 28 May 2015, at 16:06, Steve Ebersole wrote:
>
> The "next gen blog" has been "coming" for years. That's not a dig at anyone,
> just a simple point that I'd rather plan based on options I have today rather
> than options that I will have at some indeterminate date. Unless you can
> tel
On Thu, May 28, 2015 at 8:07 AM, Emmanuel Bernard
wrote:
> The banner is indeed driven by RSS
I have not seen any RSS capability from the GitHub Release "system".
> so we would lose that. Also push driven news persons would not go
> regularly to GitHub to see if anything is new.
That depe
The banner is indeed driven by RSS so we would lose that. Also push driven news
persons would not go regularly to GitHub to see if anything is new.
I forgot with who I was discussing that but we do miss a list of the releases
and their announcements. If the GitHub thing can be automated, that wo
On 28 May 2015 at 10:05, Hardy Ferentschik wrote:
> Hi,
>
> On Wed, May 27, 2015 at 09:47:29PM -0500, Steve Ebersole wrote:
>> At the moment we write release announcements using in.relation.to and then
>> announce in other mediums by posting that link. We all agree (more or
>> less) that the wiki
Hi,
On Wed, May 27, 2015 at 09:47:29PM -0500, Steve Ebersole wrote:
> At the moment we write release announcements using in.relation.to and then
> announce in other mediums by posting that link. We all agree (more or
> less) that the wiki editor and rendering on there leaves much to be desired.
At the moment we write release announcements using in.relation.to and then
announce in other mediums by posting that link. We all agree (more or
less) that the wiki editor and rendering on there leaves much to be desired.
Brett had mentioned a long time ago about GitHub and its release
capabiliti
