Re: Distros project

[Nadim Shaikli <shaikli at yahoo dot com>]

--- Muhammad Alkarouri <malkarouri at yahoo dot co dot uk> wrote:
>  --- Nadim Shaikli <shaikli at yahoo dot com> wrote: > --- 
> > Yeah, I'm looking forward to the SAIS doc (formerly
> > LAS) this coming sunday from Mr. Alkarouri.
> 
> Will come in time, in shaa Allah.

Great, I just saw a commit of las.sgml - I'll be asking
Eluzbeir to do his magic to rename that file (while
retaining its commit history) to sais.sgml

> >  2. The "distros" project has also morphed (which is
> > good) to include info on various details with regard
> > to what needs to be done from a user prospective to
> > get a distro to limp into Arabic support.
> > 
> 
> 
> The two jobs go hand in hand, you discover the where
> the problem is, you tell the user a workaround, you
> tell the developer a bug. As for dividing it in two
> documents, this is a good idea, though an alternative
> exists:
> - Maintaining a SAIS document that gives specification
> to all distros.
> - Having a correspondence channel with them. I see
> Munzir is already doing this with Mandrake, and we
> have it already for Arabbix.
> - Any requests to a distro can be filed as a bug
> report to them, mentioning the SAIS document. A bug
> document should exist in Arabeyes showing the current
> Arabic-related bugs, a suggestion already made.

Agreed. 

> > I doubt they'd be
> > interested in a 20-page document; from their
> > prospective they'll want to
> > see a list
> > or a table of what we require for proper Arabic
> > support and what we deem
> > broken in their respective distros (not even the
> > fixes just yet) and some
> > reference (contact info, further details, etc).
> 
> No one is interested in a large doc, I agree. May be
> the list/table is similar to the bugs page, so we
> unify these.

I think this is key with regard to distro creators and
maintainers.

> I got you now, actually. Though it's not very
> different from what we are doing. Remember that all
> docs are currently evolving.
> May be if we have a hierarchy of:
> SAIS
>   |------|--------------|
> MAPS    Arabbix APS    Fedora APS
>   |
> Mandrake Howto ...
> 
> with howtos easily accessible from outside.

Yup, this sounds very resonable.  The APS docs being
those simple list/tables of what the distro owners
should consume.  Your logical hierarchy is strictly
symbolic and doesn't need to be in CVS of course.

In the distros CVS we currently have,

 TODO.sgml              ; this is Great, do please update
 apps.sgml              ; this is a list of apps we want ?
 las.sgml               ; will be renamed to sais.sgml
 arabicsupport.sgml     ; Generic howto,  right ?
 mdkarabicsupport.sgml  ; Mandrake howto, right ? rename ?
 rharabicsupport.sgml   ; Redhat howto,   right ? rename ?
                          Redhat to be Fedora ?

> Disclaimer: This thread of discussion has nothing to
> do with the fixed release date of the next SAIS
> document. Don't expect any of the ideas here to be
> included in the immediate next version. Some may,
> though.

No problem, sounds like we are on the same footing and
that's all that matters.

BTW: we have a committed Mandrake inspector (Munzir), do
     we still have you as a Fedora inspector ?  Are there
     any out there interested in doing this for Debian ?

Salam.

 - Nadim


__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree