The tools still have some issues, and they do need to be resolved but we are going to concentrate on the repository first.
I like many of your ideas here, and I think we should do it. The only real risk (besides time to implement) is that the community will not be big enough to make things dynamic. I think thats not a huge risk though, at least, its a risk worth taking. Would you mind taking a few minutes and writing up the individual features you would like to see so that we can put them in the queue of consideration? El oct 27, 2010, a las 2:51 p.m., Torben Hoffmann escribió: > A few thoughts from a casual user... > > Why would one want to use a repository? > > Well, you would like to get good code that helps you become more productive > by not having to do everything by yourself. > > But how do you find good code that can help you with your particular problem? > > If I go to the Erlware repository on the web I get a flat list - not optimal. > If I go to CEAN I get a break-down based on the type of application and one > lien about each application - this is a bit better, since it gives me an idea > about if a certain application could solve my problem. > If I go to trapexit.org (this is by memory since that site down right now) I > get a web-crawled list of application from all over the place - again with a > one-liner as explanation, that might give me a hint about the chance of > finding something to solve my problem. > > If I go to http://boardgamegeek.com/ then I can easily search, browse and > what-have-you regarding board games - news, descriptions, reviews, ratings, > session stories, alternative game rules, version information et cetera. > Try to navigate around a bit and I think you can see how it works. > > This is what I want for software - this is where I think Erlware should aim > to go. > > I want to hear from people if they use a given package and how much they like > it. > I want to hear from people how they use it. > > Github has some of this, but I would like to detach the author part from the > user part by having a community of users instead of a community of > developers. I think this will lead to better information. > I want Wikipedia + Amazon + Github in one wrapping. > > This is by no means an easy task, but I think that this is what will make a > significant difference. > > The current situation with Erlware - in my view - is that the tools have > reached a level of maturity that allows you to build something on top of > them. But something on top is needed in my view. > > Cheers, > Torben > > > On Wed, Oct 27, 2010 at 19:35, Eric Merritt <[email protected]> wrote: > Samuel, > > You are basically echoing what me and martin have been talking about as > well. That is the direction we are definitely planning to go. It doesn't mean > we wont be doing any tools work. There are many incremental features that we > would like to add, but it does mean building a rock solid repository with a > very good packaging spec. Thats our goal right now and probably what we will > talk about in this first call. > > We have a few ideas floating around for doing that, we will probably talk > about it a bit on thursday. > > In any case, you are absolutely right that is where our focus must, must, > must be. > > Eric > > El oct 27, 2010, a las 11:42 a.m., Samuel escribió: > > > Hi all, > > > > I most likely wont be able to attend the meeting, but I already > > discussed with Martin my view on the project (sadly, I admit I'm > > becoming less and less involved). The most relevant point I tried to > > make is that I felt that the main goal I understood Erlware was > > pursuing was something like "building a strong software community > > around a trusted and reliable repository of open source erlang > > products." However, much effort is put in the tools around the > > repository and little in the repository itself. > > > > That's not to say that focusing on the tools is a wrong idea, but that > > that project, always in my view, was drifting apart from the original > > idea. That could essentially for three reasons: either my idea of > > "original idea" was wrong, or the original idea was wrong, or the > > strategy was wrong. > > > > Just something I'd like to know your thoughts, cause I'm sure you were > > thinking a lot about this :) > > > > Best > > > > On 27 October 2010 17:24, Eric Merritt <[email protected]> wrote: > >> Everyone, > >> > >> As many of you know the core group of Erlware guys have finished up > >> nearly all the things that have been eating so much of our time for the > >> last few years. Now it is time for some serious heads down development of > >> Erlware. To that end we implementing a few interesting changes. > >> > >> Martin and I often have conversations about the direction and we are > >> planning to take. We recently realized that these conversations are > >> massively important to the direction of our project. However, we would > >> very much like to let in the Erlware community. So we are going to try a > >> weekly conference call, where the core group of folks at Erlware is going > >> to plan directions and talk about problems. We encourage participation, > >> but if you would just like to listen that is perfectly fine as well. > >> Everyone is invited and the call information is described be. > >> > >> We can discuss agenda for this first meeting in this thread. I suggest > >> that we talk lay down our general direction to get started. > >> > >> > >> 1. Please join my meeting, Thursday, October 28 at 12:30 PM CDT. > >> https://www1.gotomeeting.com/join/491562408 > >> > >> 2. Use your microphone and speakers (VoIP) - a headset is recommended. > >> Or, call in using your telephone. > >> > >> Dial +1 805 309 0014 > >> Access Code: 491-562-408 > >> Audio PIN: Shown after joining the meeting > >> > >> Meeting ID: 491-562-408 > >> > >> GoToMeeting® > >> Online Meetings Made Easy™ > >> > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "erlware-dev" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]. > >> For more options, visit this group at > >> http://groups.google.com/group/erlware-dev?hl=en. > >> > >> > > > > > > > > -- > > Samuel > > > > -- > > You received this message because you are subscribed to the Google Groups > > "erlware-dev" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > > http://groups.google.com/group/erlware-dev?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > > > > > -- > http://www.linkedin.com/in/torbenhoffmann > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
