• A good base, but....

    By Philippe Koenig 2 decades ago

    Try to apply this

    • Avoid or separate the "idea phase"
    • One project, On Nsf
    • Integrate the discussion in the NSF
    • Avoid hardcoded path, name, url etc in your code, parametrisation is so simple with notes.

      I'm not a developper, but an administrator, i try to find a helpful tools for my users to track many type of projects i hope the version 1.xxx will be the good one



      RGDS

    • Some comments inside..

      By CN=Anil Vartak/O=Notesweb 2 decades ago

      • RE :Some comments inside..

        By

        Ok, i try to explain my view "one project one nsf"

        For the moment, i'm working with around 200 developpers on 400 projects or micro-projects on SAP, DB2, Notes, Mainframe application Etc…

        Due to the diversity and the number of projects we are searching a system of repository easy to administrate, simple of use (web/notes), who can be secure, and with replication facility for the project leader.

        I think that a "big Db" with all projects is, in this case, not a good solution. But if you divide the actual DB in 2 templates (ex:Projectsbrowser.ntf & Projecthimself.ntf) you can easaly generate automaticaly a new nsf for each approved project.

        In this case you can have a more closed security around each the project, and one project can be replicate on laptop or on multiple servers without the rest of "junk" (means other projects).

        I know for the developer point of view, this is not a ideal solution, but for an administrator YES!!

        Did you have try to backup/restore a 40Gb nsf ???

        For your information, i try to find something whos between quickplace, teamroom, discussion db, but free of charged. Thus your open project seems to be a good compromise, but it need to grow up, and for the moment, i'm trying to divide it in two entities but it's sunday, the sun shine, and the bier is fresher than the laptop

        ;-)



        RGDS

        Ph koenig

        A always searching notes administrator.

        • RE: RE :Some comments inside..

          By

          OK..thanks for the clarification. Personally, I think its a bigger nightmare to handle 400 databases, each with different security than one 40 GB database, and I speak from experience because in my work environment we have over 500 databases each owned by different owners, and over 5-6 years nobody even knows exactly which database is for what purpose and whether its still being used.



          I understand your concerns about performance and the one thing we do anticipate problems with in this template is the large number of attachments for releases We do intend to have an archival system so that only the files from the latest release exist in this database and all older versions are in another database - again thats something thats in the queue. In our case, security is simple..the person who proposes the project owns it and other people on the team automatically become authors for certain types of documents (feature requests, bugs). Even with 400 projects, if each project has 100 documents its still not unmanageable, though you are getting in the realms of speed impact :-)



          I hope to have the hardcoded paths removed by next week, and we will probably be releasing a 1.x version sometime soon with minor fixes and enhancements.

  • A db per project

    By Lykle Schepers 2 decades ago

    Hmm, My first post here.

    I have been playing with this idea for a couple of years now, and I am convinced that, in my environment, it would be a good idea to have an overall db with the project details and per project a db with all the project content.



    Two reasons:

    ACL can be set per project to allow the customer access to what we are doing so that he can follow the building process. We call it the "Glass House" process.



    Also, after a project is finished, you have a perfect spot to place all the executables, code, reports, bugfixes and communications in one spot and archive it. Burn a CD and the customer has everything pertaining to the project in one go.



    For me, it works. Especially if we could aggregate all the project status's into the main db. Overall view of all the projects, nice dashboard.



    Lykle