[udig-devel] about translations in community

[Jody Garnett]

Mauricio Pazos wrote:
> Well, I am thinking in maintenance. You know that features is only a way to 
> deploy plugins, by example, axios has developed Editing Tools and Spatial 
> Operations, we decide to deploy these plugins in one features "axios udig 
> extensions", but in the future we are thinking to distribute these plugins in 
> separated features: 1-  "axios editing tools extensions for uDig" and 
> 2 - "axios spatial operations for uDig".
>   
Okay I understand; I think we should stick with having a page for each 
folder on the download site; and that page
can have installation instructions
> The cohesion in features is very light (user view point, commercial 
> convenience, license type, etc). Perhaps the criteria is to do a very light 
> documentation for feature installation and an important documentation of 
> plugins.
>   
Sounds good; we document what they can download (ie the feature), and 
then we document what that thing does (probably tools, dialogs, wizards 
... users don't know about plugins).
> May idea is: 
>
> FEATURE DOCUMENTATION
> 1. Content: 
> Plaugin Name  | Documentation
> --------------------------------------
> AAA-plugins    |        url AAA usr guide
> BBB-plugins    |        url BBB usr guide
> CCC-plugins    |        url CCC usr guide
> DDD-plugins    |        url DDD usr guide
>
> 2. Install:
> stpe1:  ----
> step2: update site
> step3
>
> 3. Test your instalation
> ....
> 4 Support
>
> support at xxxx.net
> tel: ..
> fax: ..
>
> Then we could change the deployment criteria (features) without many changes 
> in the documentation.
>   
Yeah I like that a lot :-) I will try out that format on my feature and 
see how it works.
Jody