[arch-haskell] Where are we headed?

[Xyne]

Hi,

As mentioned in the other thread, I contacted Kaiting about hosting for the
Arch Haskell group. Here's the reply:

Kaiting Chen wrote:

> Hi Xyne, so you know that for a while I've been trying to get a new server
> up on EC2. It's just about done, so if you guys don't mind being test
> subjects I'd like to set you up there. Note that the new server is built on
> ephemeral storage and thus in the case of a hardware failure all data will
> be lost. On the other hand it is backed up every thirty minutes. If you need
> greater granularity than that please keep critical data in an off-location
> version controlled store. Disk space and bandwidth are not a problem at the
> moment, and I'll let you know if they will be.
> 
> I believe that ACL's are supported. That is the preferred way of sharing
> things right now. Let me know if you need anything beyond that.
> 
> And if you guys are hosting a repo, I can set up a VirtualHost for you.
> 
> Kaiting.


I replied to say that it sounds good and that I don't think we'll need finer
granularity. I also said that I wanted to discuss the name of the VirtualHost
with the team before setting it up.

So, what do you think?




> simons:
> > Hi guys,
> > 
> > there seems to be a lack of coordination. It feels like we are wandering
> > off into all kinds of different directions. I would like to think that
> > there is a common goal that we are trying to achieve, but I'm not sure
> > whether that is the case. Maybe it would be helpful if everyone involved
> > in this effort could post a short description of what exactly it is that
> > he or she is interested in accomplishing?
> > 
> > Personally, my goal is to provide a stable and reliable distribution of
> > Haskell packages that ArchLinux users can easily build and install.
> > Whether those packages are distributed in binary form or whether they're
> > available on AUR is irrelevant to me. My main interest lies with the
> > file tentatively called "PKGLIST" [1]. That file is hard to come up
> > with, and it's particularly hard to maintain in the presence of constant
> > updates that mutually exclude each other.
> > 
> > Now, if we had a consistent package list, then we could easily use it to
> > update AUR or build a binary repository. Without a consistent package
> > list, however, we can do neither.
> > 
> > Take care,
> > Peter



Don Stewart wrote:

> Can I suggest that the new team declares a strategy, then describes a 
> policy to implement that?
> 
>     http://haskell.org/haskellwiki/Arch_Linux/Policy
> 
> Always good to write down what you're trying to do.
> 
> :-)
> 
>     
> -- Don

I suggest that the new team declares itself first. ;)

It may be a good time to do this now as we will need to set up accounts for
team members on the aforementioned server.

As for my part in it all, I hope to do the following:

* contribute and collaborate on tools for managing binary and source repos on
  the server, along with generally helping to manage the server

* provide tools for users to work with packages (installation, building from
  source, etc)

* help in my capacity as a TU by supporting packages in [community] and the
  AUR, and eventually [extra] if my help is wanted

* help out with whatever else I can


/Xyne