Community » BeWelcome Forum

Sorry - I already have one answer - I know where to download the source code from...

Cheers,

Peleg. 

Hey Peleg, good to see you here.

Let me answer about the (c) at the bottom of the page first:

1) You're totally right ;) although I think, this is more something like the typical reaction that a lot of people have when writing webpages: put a name and copyright on it. We released the project under open source just a while ago and couldn't go through all the files yet. Plus: Not everyone in the project is familiar with open source projects yet

2) Although we just put online the latest release, nobody cared about the footer I think. It's needs a redesign anyway. Let me take care of that the next days and weeks :)

About your second question - Quote:
Can you explain the line: "We reserve the right to collect further personal information from you that we do not post on BeWelcome?

This might be your address data (that you can set hidden on the BW-site) or information about your status as a volunteer, messages and posts you wrote, pictures that you uploaded or other things like that. Nothing mysterious actually. It's more a legal term imo. By the way: The terms, statutes and so on are mainly edited by BeVolunteer (the organization behind BeWelcome) and the BoD (Board of Directors of BeVolunteer). They (Well, I'm part of it. Just wanted to say that it's not some abstract entity) are responsible in case of legal problems.

Would be great to have you in the team. Looked over your pages a bit - a lot to read ;) You have to teach me hebrew aswell though...

Drop a line to me (http://www.bewelcome.org/user/lupochen) or Philipp - Dev Team Coordinator (http://www.bewelcome.org/user/philipp) or we send you an email these days!

so long

Micha

-----------------

dev.bewelcome.org

About the (c): for what I know nobody never talk about it. I see that Lupochen answer and said it was something to change.

 I am not at all an expert about GPL Licence, I don't know if this (c) is important (does it mean copyright when we want copyleft ?)

If you believe it is important please explain it a bit more, I am sure it can motivate people.

 I browsed the FAQ without any answer about the licenses. I'm up to make the missing pages if someone give me the infos.

Since the exception of beWelcome (compared to the others hopitality networks) is to be based on an open source project, I think this issue is very important to improve and make it clear for everyone...

the answer came from the Open source group :  http://www.bewelcome.org/forums/s869-what_about_the_exact_status_over_here__

I read this, wich is pretty clear  http://www.gnu.org/licenses/gpl-howto.html

@crculver, good to see someone willing to help !

 Peter is the man for your request, try send him a BW message, he always answer.

In the meanwhile , you will find everything you need on: http://www.bevolunteer.org/trac ;

BW Framework is rox, it is based on PT. I think it is not that bad, but true, it is not Zend or CakePHP.

Be happy not be compelled anymore in using what people call Old BW which was even more specific (It was the first version I made in a rush in end 2006, not even a MVC).

Probably in some time (2/3years ?) we will start a move to something more powerful, living BW Rox, but, they are currently no plan to change it, since we have not yet found a dead end with this current system (except that you are to invest a bit of energy in understandting how it works, but is is very classical in fact).

I strongly suggess that  you setup a local environment, choose an easy ticket and propose a fix. If so I am sure that the DEV Team  will pay attention.

If you need some help, feel free to conatct me, I usually answer in less than 24h00

JeanYves

There is a discussion somewhere but I am not following it accurately (I am more focused on current bugs).

Nota: several things look intersting with Drupal, but this would be very certainly a big big thing to switch to it

A lot has been written about Drupal vs not Drupal. I don't remember where exactly, I guess somewhere on the wiki or trac, but very much on the mailing list.

One critical (yet unanswered) question was if regular release management  would be as robust and easy as it is now. Right now most functionality is defined in the code, so a release basically means to update the codebase. Drupal does much more in the DB, so this can be more tricky. And, you don't see on SVN if someone has created a new content type via the admin interface (content types typically live in the DB only).

Imo, IF we want to try Drupal, the way to go would not be, as you say, that the core devs do the move, and others jump in later. Instead, I would say, one person who actually knows Drupal more than others (one day that could be myself) makes a public demo install, and we can see how it works.

Technically it would be a completely new and different project. 

Hiya

@crculver: you should be able to find me on skype, irc, yahoo, gtalk or msn. Irc is probably the easiest (#bewelcome-dev on freenode).

As far as the framework discussion is concerned, it's still alive (well, not that much discussion right now, but the intent and motivation is still there). I still want to try moving BW to the Zend framework just haven't had that much time so far.

I don't think the way to do this is have the team switch things to a new platform. I think the way to do it is in a number of steps: 1) get the current codebase up to a point where it's consistent and uses as few things from the frameworks as possible (and by few I mean 'uses only the BWRox code' instead of 'uses BWRox and Platform PT, etc') and 2) start a new branch for the different frameworks we'd like to test, i.e. Zend and Drupal. Then we can see how easy it is to switch and how far we can go before we run into major problems - without making changes to the current setup. If/when we've got a stable build using another framework we can the switch.

The timeline of this is 'future': we currently have lots of stuff to do to make sure things work properly and are nice to use. But like I said, that doesn't mean it's been forgotten at all :) Had some emails with Steinwinde who is still interested in the topic as well and was looking into it - and it's obviously on my todo list as well.

That being said, I agree with Midsch that it's more important to get the userbase of BW growing - and I don't think that any single feature/group of features we could add would really result in a massive increase. I think different things are needed, most of them social in nature.

For the record: I'm not a fan of drupal but that's most likely because I've never used it. I won't be championing it but if someone is interested in experimenting with a framework switch to drupal I'll be more than happy to help with the sysadmin stuff (SVN, etc) as I'd love to see if BW is portable to drupal.

Regards

Peter

I would remove the c  as BV don't own the name right of BeWelcome.

But that is just my uninformed opinion. 

anyway off topic