Re: [viewvc-dev] Best Way to Collaboratively Customize ViewVC?

David T. Ashley wrote:
> Hi,
>  
> I'm a user of an older version of ViewVC.
>  
> Our software developers are working on a collaborative database in PHP. 
> We'd like to integrate ViewVC into this, in the sense that ViewVC should
> recognize session cookies issued through our login process, validate
> them (MySQL queries), and display error screens if a user isn't logged
> in.  We plan to customize ViewVC to do this.
>  
> Customization is the easy part (it is just standard server-side web
> database programming).
>  
> The hard part is:  What is the best way for us to collaborate with the
> ViewVC community and make our work useful to others?  Is there any
> provision in ViewVC for "variants" or "patches"?  Or do we just
> customize the code and leave the end result on the web somewhere?
>  
> What is the best way to collaborate?

In the past, folks who've customized ViewVC for their own purposes have made
patches available either from their own websites or via ViewVC's own issue
tracker, where live many PATCH issues that may or may not eventually get
integrated into ViewVC itself.  I suppose another method would be for you to
commit your changes to a branch in the ViewVC source code repository, or for
a ViewVC committer to do so on your behalf.

-- 
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGipG4okEGqRcG/W4RAqA9AKCmkP1/ji/G87UKcWQ0Xqh51Oc4RgCgpBXL
JwPh9AApbtzFLsbfz6o3D2s=
=MFQ4
-----END PGP SIGNATURE-----