Em 08-11-2010 21:44, Gustavo Sverzut Barbieri escreveu:
> On Mon, Nov 8, 2010 at 7:32 PM, David Seikel<onefang@...> wrote:
>> Is requested, here's a thread about fixing up other stuff on the web,
>> apart from the content which is handled in the "web site contents"
>> Can someone with a clue fix up TRAC? Personally I have no clue about
>> TRAC. If my recent experience is any guide, no one can just create an
>> account and start using it, all they get is error messages, no ability
>> to comment on or create stuff. That's one BIG turn off right there. I
>> was trying to do the right thing about the focus bugs, but failed
>> completely to be able to figure out how to actually enter any useful
>> text, and I'm a very experienced developer. I even asked on the mailing
>> list with no reply other than "yeah, you get those error messages until
>> raster manually recreates your account". Not even a "i've fix0red your
>> account dave" message from raster. Certainly no "the button to make
>> comments or create new bug tickets is in THIS bleeding obvious place
>> you blind moron" reply.
>> So linking things to TRAC is kinda pointless, until it works right.
> I guess we have no TRAC expert in the community. However, simple TRAC
> installations are easy, someone with bit of linux skills + time could
> install a new version of trac and configure it properly, do some tests
> and then we migrate the database data.
> I guess the problem with login are actually two: 1) incorrect setup of
> trac with its database; 2) too strict policy that people added to
> avoid spam. Right now I just use trac in closed environments, but I'm
> pretty sure there are plugins to employ captcha for
> registrations/login -- just need time to look at those.
> The other annoying bug is the replication of attachments/images in
> every trac page. I'm also sure this is an installation problem, as
> none of ProFUSION internal tracs have such issue.
> So what we need is basically someone with time willing to do it. You
> can do it at your own machine and check how it works, then we'll grant
> access to the one willing to do it at our servers. You should
> research other project trac installations, like VLC, and check out for
> useful plugins and configuration parameters.
>> Inc had said -
>>> one additional thing that needs some major love is exchange. It needs
>>> to be rewritten and worked into the main site.. it looks like shit
>>> and the maintainer left the project. Also it was built off of some
>>> random framework. The new solution should not be framework based
>>> because that just makes things more and more difficult for us. IF
>>> anyone is willing to help feel free to jump in! also the donate page
>>> needs some love, I would love to start back up bounties as well as be
>>> able to cover various other different things for the project!
>> Which might fall into this category to.
> exchange aimed to be a provider of EFL stuff and thus use EFL stuff to
> do it, like use of Edje and providing meta data to download it
> directly from apps, like e17 theme.
> That is the reason for specific setup. However, I'm quite sure we
> don't have manpower to invest on it. Not just the server side, but the
> client side as well.
> Given that, I'm all for dropping libexchange (move to OLD) and
> associated web services and request an external server hosting like
> gnome-look.org, kde-look.org, gnome-apps.org, kde-apps.org. We really
> have bigger fish to fry atm.
I have also deployed Trac linked to Subversion at my workplace, so
I can perhaps help with this.