Around April, I got myself a new server that I planned to be dedicated to all things gdc.  Initially it provided a default web page - which will soon have useful links to development, bugs, build releases for various architectures / platforms, etc.

http://gdcproject.org


Wanting to move away from the bitbucket wiki, and generally being annoyed at github wiki. I'd thought I'd host my own.

http://gdcproject.org/wiki

Yeah yeah yeah, it's a bit ugly, but if anyone is any good at theming moinmoin, or has any useful themes to offer, please point me in the right direction or perhaps arrange to have access granted to the server. :-)


And for the same reasons as above, with the extra reason that D's bugzilla now disallows creating new bugs for GDC, I've also installed a new bug tracker on the system too.

http://gdcproject.org/bugzilla

I'm going to see if I can get it hooked up to a mailing list for users to register to, or (with permission?) link my bugzilla installation to this mailing list.


As ideally I will be wanting to archive off the bitbucket repo to prevent further use in the future, and turn off github issue tracker completely (once the initial issues some people have raised have been moved or closed down).  I am proposing that people start using the following links provided as the means of further contributing all documentation and bug raising through these new channels if you don't mind updating your bookmarks.  However all will be subject to just how well it goes getting the last few pieces set-up. =)

Any comments / suggestions.  Please feel free to provide them.


Regards
Iain

On Mon, 9 Jul 2012, Iain Buclaw wrote:

> Around April, I got myself a new server that I planned to be dedicated to all things gdc.  Initially it provided a default web page - which will soon have useful links to development, bugs, build releases for various architectures / platforms, etc.
> 
> http://gdcproject.org

Food for thought, make sure someone has automated off-site backups.
Protecting against single-person hosted sites and them disappearing is
important for long term health.  For example, Walter downloads a nightly
dump of the dbugs data base from my system.

> And for the same reasons as above, with the extra reason that D's bugzilla now disallows creating new bugs for GDC, I've also installed a new bug tracker on the system too.
> 
> http://gdcproject.org/bugzilla
> 
> I'm going to see if I can get it hooked up to a mailing list for users to register to, or (with permission?) link my bugzilla installation to this mailing list.

The gdc category was disabled at the bugzilla I host by request of someone on the gdc project ages ago.  I don't remember who.  I'd be happy to re-open it and give admin access to one or two people.  Having it report changes to a list or a newsgroup is pretty easy to setup.

Later,
Brad

On 10 July 2012 08:42, Brad Roberts <braddr@puremagic.com> wrote:
>
> On Mon, 9 Jul 2012, Iain Buclaw wrote:
>
>> Around April, I got myself a new server that I planned to be dedicated to all things gdc.  Initially it provided a default web page - which will soon have useful links to development, bugs, build releases for various architectures / platforms, etc.
>>
>> http://gdcproject.org
>
> Food for thought, make sure someone has automated off-site backups. Protecting against single-person hosted sites and them disappearing is important for long term health.  For example, Walter downloads a nightly dump of the dbugs data base from my system.
>

Will have to get that done eventually... if only there was someone who I can trust. :o)



>> And for the same reasons as above, with the extra reason that D's bugzilla now disallows creating new bugs for GDC, I've also installed a new bug tracker on the system too.
>>
>> http://gdcproject.org/bugzilla
>>
>> I'm going to see if I can get it hooked up to a mailing list for users to register to, or (with permission?) link my bugzilla installation to this mailing list.
>
> The gdc category was disabled at the bugzilla I host by request of someone on the gdc project ages ago.  I don't remember who.  I'd be happy to re-open it and give admin access to one or two people.  Having it report changes to a list or a newsgroup is pretty easy to setup.
>

I don't think that would be needed now, but thanks.  Yes it would be useful to co-ordinate bugs raised in gdc that are really bugs in D frontend.  But this is an increasingly rare occurrence.

Last two that spring to mind go way back to April 2011: http://d.puremagic.com/issues/show_bug.cgi?id=5349 http://d.puremagic.com/issues/show_bug.cgi?id=5735


Hope you don't mind, but I have instead set up my own issue tracker to report changes to this list, however on the initial test I did yesterday I seem to have been getting responses back from d.gnu-bounces with the message "Your message to D.gnu awaits moderator approval".   I was under the impression that an email address only needs to be subscribed to the ML to get past this block? Apparently this is not the case. :-)

The email address the issue tracker is using to send to D.gnu is gdc-bugzilla [at] gdcproject [dot] org.  And it is using sendmail with postfix incase that would be a problem.   If you are able to lift the moderator restrictions, I could send another test here to confirm all is ready to go.


Regards
-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';

Iain Buclaw, el 10 de July a las 09:17 me escribiste:
> >> Around April, I got myself a new server that I planned to be dedicated to all things gdc.  Initially it provided a default web page - which will soon have useful links to development, bugs, build releases for various architectures / platforms, etc.
> >>
> >> http://gdcproject.org
> >
> > Food for thought, make sure someone has automated off-site backups. Protecting against single-person hosted sites and them disappearing is important for long term health.  For example, Walter downloads a nightly dump of the dbugs data base from my system.
> 
> Will have to get that done eventually... if only there was someone who I can trust. :o)

You don't really need to trust anyone, what you want to backup is publicly available anyway, right? Then you can make a tarball or something and just publish it in some obscure path in the web. Then anyone willing to do a backup only have to download that tarball. If is not too big, you could also open a gmail account and send the tarball to that account (I did this for backing up a small server).

> > The gdc category was disabled at the bugzilla I host by request of someone on the gdc project ages ago.  I don't remember who.  I'd be happy to re-open it and give admin access to one or two people.  Having it report changes to a list or a newsgroup is pretty easy to setup.
> 
> I don't think that would be needed now, but thanks.  Yes it would be useful to co-ordinate bugs raised in gdc that are really bugs in D frontend.  But this is an increasingly rare occurrence.

Maybe when GDC gets merged this could change, as the I think the userbase of GDC could grow a lot. But even then, maybe is not too hard to move a bug from one bugzilla instance to another.

Also, did you tried to put your infrastructure in gcc.gnu.org, as other languages tend to have they home pages in gcc.gnu.org/lang, it might be a good idea to have something like gcc.gnu.org/d. But maybe you want to have more control over the server and I guess you can't really request that until GCD is completely merged. Just thinking out loud. :)

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Si por el chancho fuera, se autocomería con chimichurri Worshestershire!

On 10 July 2012 12:45, Leandro Lucarella <luca@llucax.com.ar> wrote:
> Iain Buclaw, el 10 de July a las 09:17 me escribiste:
>> >> Around April, I got myself a new server that I planned to be dedicated to all things gdc.  Initially it provided a default web page - which will soon have useful links to development, bugs, build releases for various architectures / platforms, etc.
>> >>
>> >> http://gdcproject.org
>> >
>> > Food for thought, make sure someone has automated off-site backups. Protecting against single-person hosted sites and them disappearing is important for long term health.  For example, Walter downloads a nightly dump of the dbugs data base from my system.
>>
>> Will have to get that done eventually... if only there was someone who I can trust. :o)
>
> You don't really need to trust anyone, what you want to backup is publicly available anyway, right? Then you can make a tarball or something and just publish it in some obscure path in the web. Then anyone willing to do a backup only have to download that tarball. If is not too big, you could also open a gmail account and send the tarball to that account (I did this for backing up a small server).
>

Publicly available to download might be one thing, but only works if
someone is willing to retrieve it.  :-)
Gmail account would be under lock and key by me, unless I give someone
else access to it.


>> > The gdc category was disabled at the bugzilla I host by request of someone on the gdc project ages ago.  I don't remember who.  I'd be happy to re-open it and give admin access to one or two people.  Having it report changes to a list or a newsgroup is pretty easy to setup.
>>
>> I don't think that would be needed now, but thanks.  Yes it would be useful to co-ordinate bugs raised in gdc that are really bugs in D frontend.  But this is an increasingly rare occurrence.
>
> Maybe when GDC gets merged this could change, as the I think the userbase of GDC could grow a lot. But even then, maybe is not too hard to move a bug from one bugzilla instance to another.
>

There is a 'See Also' where you can link in external bug urls to your report.


-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';

Iain Buclaw, el 10 de July a las 14:10 me escribiste:
> > You don't really need to trust anyone, what you want to backup is publicly available anyway, right? Then you can make a tarball or something and just publish it in some obscure path in the web. Then anyone willing to do a backup only have to download that tarball. If is not too big, you could also open a gmail account and send the tarball to that account (I did this for backing up a small server).
>
> Publicly available to download might be one thing, but only works if someone is willing to retrieve it.  :-)

Of course, I thought you were concerned about security risks on giving access to the server to somebody else to make a backup.

> Gmail account would be under lock and key by me, unless I give someone else access to it.

Yes, using gmail was a suggestion as an alternative "someone willing to retrieve it". I mean, just using gmail as storage for your own backups.

--
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Geckos can stick to any surface, with the exception of Teflon, which was
specifically engineered to prevent even van der Waals adhesion.
	-- "Research into Gecko Adhesion", Berkeley, 2007-10-14