[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [admin] Updates on the new website



Salam,  

                 في ح، 12-02-2012 عند 18:58 +0200 ، كتب Mohammed Sameer:
> > Seriously, the Arabic translation of drupal 7 is (or at least was when
> > we started) incomplete and there is a big warning about views for drupal
> > 7 on http://drupal.org/project/views so we (Youssef and me) decided to
> > use drupal 6 for now.
> 
> I used views despite the warning :D
> 
> It worked fine for me but no it seems that views is ready.
> The only _practical_ advantage I see with Drupal 7 is that we won't
> have to worry about upgrading it soon.
> 
> I guess drupal 7 offers better content translation support. I guess we
> can also get that with drupal 6 but it might be a pain to update to 7 :(

I don't have any problem with drupal 7 despite the warning (I even
installed the test instance with drupal 7 at first). Here is another
test instance running drupal 7:
http://abderrahim.arablug.org/arabeyes-d7/

> However if the translation is incomplete then we should either:
> 1) Stick to drupal 6 and work on the translation.
> 2) Jump to drupal 7 and fix the translation _if it won't take a long time_
> I guess we will have to update to drupal 7 anyway at some point and we need
> to have the translation there but I'd rather not stop the website efforts just to
> fix the translation.

I see Abdalrahim has already offered to start a translation campaign :)
I'd like to delay this until the website is complete, and start a
translation campaign for all the site (including every module we might
end up using) just before the launch.

> Mailman is a "bit" painful ;)
> We can always First make it run then make it run better!

OK

> > > >       * wysiwyg allows to integrate editors (like tinymce) in drupal
> > > >         (which is nice, although I'm not sure this is really needed).
> > > 
> > > I'd not use it since normal people will not be posting anyway but that's
> > > just my opinion.
> > 
> > OK
> 
> At least Fakhouri thinks it's needed so we need to investigate this.

I'm fine either way, as it's really simple to set up.

> > Looks nice, but doesn't seem to be available for drupal 7...
> 
> The module is very minimal. I'm sure I can port it fast if needed.

OK, but let's get the thing to work first, and then make it better ;-p

> What we can do is to use drupal 6 + node_import to import the content then
> upgrade to drupal 7 :P
> 
> I can also write a simple importer that can be invoked via drush if needed.

Sorry if it's more work for you, but I prefer the latter.

> The problem when I started working on the drupalification of arabeyes is that
> we didn't know what's needed from the website. If we know that now then it will
> make the process way easier.

IMO, nobody is using the current site, so it isn't a problem if we don't
have all the features. For me, the only important thing is to have
project pages that contain informations and updates/announcements. (I
also think the website should be slightly less formal).

> > For the blocks on the right sidebar (listing projects for each
> > category), I think it is easy to do them using views. But how about
> > project pages? like this one:
> > http://projects.arabeyes.org/project.php?proj=GNOME
> > How can one do something like this?
> 
> If we want something minimal then:
> 1) Each project is a custom CCK node.
> 2) Contributors are assigned via the user reference field.
> 3) Notes for projects are another content type done via CCK.
> 4) Each note references its parent project via node reference
> 5) http://drupal.org/project/nodereference_url can be used to put an "add note" link
>   to each project.

That is enough IMO. But what's needed to actually show the notes below
the project informations?

> 6) Permissions will be a bit complex:
>    - Users referenced as contributors will be given update access to the project
>      using http://drupal.org/project/nodeaccess_userreference
>    - Only contributors can create notes and this is done via http://drupal.org/project/nodeaccess_nodereference
> 
> The permissions part is really complex but it depends on what we want from each project node!

I guess we can leave this to the "make it run better" part.

One other thing that would be useful but can wait for now is how to
handle todos, I've seen a few modules but most of them don't work with
drupal 7 (I guess this could replace Abdalrahim's
calendar-for-tracking-deadlines).

Regards,
Abderrahim