Community
    • Categories
    • Recent
    • Popular
    • Users
    • Search
    • Register
    • Login

    Development documents?

    Scheduled Pinned Locked Moved Development
    6 Posts 3 Posters 4.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      morphje
      last edited by

      Hi,

      First of all, the emailadress entwickler@i-doit.org doesn't work, but i still want information regarding development for i-doit. could you please provide me with that info?

      ps. yes i'm new and no, i will not introduce myself. I will let my actions speak for itself, not my words (and it takes too much typing how old i am and where i was born) 😛

      1 Reply Last reply Reply Quote 0
      • _Chekov__
        _Chekov_
        last edited by

        @morphje:

        Hi,

        First of all, the emailadress entwickler@i-doit.org doesn't work, but i still want information regarding development for i-doit. could you please provide me with that info?

        ps. yes i'm new and no, i will not introduce myself. I will let my actions speak for itself, not my words (and it takes too much typing how old i am and where i was born) 😛

        Hi morphje,

        well I would say after your "introduction", don't expect too much feedback for your enquiry. 😉
        Anyways, main online documentation is (was) intended to be found at http://doku.i-doit.org/wiki/Main_Page
        but the page does not offer too much documentation even from the general point of view for the
        i-doit software.

        In addition to that I think the source files are worth of effort to take a look at in terms figuring out
        how the system has been made. As far as I know, i-doit is rather modular in its design, so that's
        a good starting point to keep in mind.

        Under the installation path of i-doit, you'll find a subdirectory named doc, which again is split in
        sections developer and user. There you can find some additional information as well.

        Perhaps you have some great ideas of furthering the product with some useful modules to
        connect i-doit with some incident management system, other than OTRS ..?

        With kind regards,

        Chekov

        Chekov is using i-doit v1.6.4 PRO in production & i-doit v1.7 PRO in test

        1 Reply Last reply Reply Quote 0
        • M
          morphje
          last edited by

          okay …. i warned you 😛
          The name is patrick, i was born in denhelder a small town up north of the beautifull country of holland. This all happend in the year 1981. Etc, bla bla

          The source files are offcourse nicely coded and well commented and the txt files in the doc directory are also a helping hand. But i was under the impression that there was a huge documentation base when i e-mailed 😉

          Great idea's so far are "automatic" inventory for software and hardware (h-iventory) and perhaps some barcode assisted supply management module. As far as OTRS goes, i'm not sure about that, because we have an ERP system here in which i could intergrate the incident part.

          1 Reply Last reply Reply Quote 0
          • _Chekov__
            _Chekov_
            last edited by

            @morphje:

            The source files are offcourse nicely coded and well commented and the txt files in the doc directory are also a helping hand. But i was under the impression that there was a huge documentation base when i e-mailed 😉

            Great idea's so far are "automatic" inventory for software and hardware (h-iventory) and perhaps some barcode assisted supply management module. As far as OTRS goes, i'm not sure about that, because we have an ERP system here in which i could intergrate the incident part.

            Hi Patrick,

            back then when I first got interested in i-doit project, I read from here
            and noticed from installation documentation that "the place to be" regarding
            i-doit documentation is that dedicated wiki-site http://doku.i-doit.org/wiki/Main_Page.

            Practically speaking, there's absolutely no activity on wiki-site and efforts to provide
            even minimal useful information regarding i-doit installation and usage at various degrees
            is nonexistent.

            Oh and not to mention that wiki-documentation is sort of outdated, but I believe this
            will change somehow after i-doit v0.9.1 got officially released.

            Could you please describe how that "automatic" inventory for soft- and hardware should work?
            Based on i.e. barcode based reading and transport of data into the system?

            I am also not using OTRS for incidents, rather some other product. Integration of i-doit for our
            existing incident / helpdesk system should be possible somehow.

            Now as I come to think of it, it could be theoretically sufficient enough to have changes/adds/deletes/etc
            emailed over to desired email address, which then again is dedicated for i-doit incidents. That would be
            the first step how to gather and get noticed of some changes what has been done to i-doit system.

            With kind regards,

            Chekov

            Chekov is using i-doit v1.6.4 PRO in production & i-doit v1.7 PRO in test

            1 Reply Last reply Reply Quote 0
            • N
              npotthast
              last edited by

              @_Chekov_:

              Practically speaking, there's absolutely no activity on wiki-site and efforts to provide
              even minimal useful information regarding i-doit installation and usage at various degrees
              is nonexistent.

              If you don't mention this forum…

              Oh and not to mention that wiki-documentation is sort of outdated, but I believe this
              will change somehow after i-doit v0.9.1 got officially released.

              There you have guessed right. After releasing version 0.9.1 we will certainly have more time to update the documentation.

              MfG,
              Niclas Potthast

              1 Reply Last reply Reply Quote 0
              • M
                morphje
                last edited by

                @_Chekov_:

                Hi Patrick,

                back then when I first got interested in i-doit project, I read from here
                and noticed from installation documentation that "the place to be" regarding
                i-doit documentation is that dedicated wiki-site http://doku.i-doit.org/wiki/Main_Page.

                Practically speaking, there's absolutely no activity on wiki-site and efforts to provide
                even minimal useful information regarding i-doit installation and usage at various degrees
                is nonexistent.

                Oh and not to mention that wiki-documentation is sort of outdated, but I believe this
                will change somehow after i-doit v0.9.1 got officially released.

                Could you please describe how that "automatic" inventory for soft- and hardware should work?
                Based on i.e. barcode based reading and transport of data into the system?

                I am also not using OTRS for incidents, rather some other product. Integration of i-doit for our
                existing incident / helpdesk system should be possible somehow.

                Now as I come to think of it, it could be theoretically sufficient enough to have changes/adds/deletes/etc
                emailed over to desired email address, which then again is dedicated for i-doit incidents. That would be
                the first step how to gather and get noticed of some changes what has been done to i-doit system.

                With kind regards,

                Chekov

                Sad to hear that activity surrounding documentation is rather non-existant.

                "Automatic" updates. Simple, you create a computer and add the systemID to it, at logon you run the script from H-inventory and upload it to i-doit, which in turn updates the "hardware-card" with the information. In that case all hardware is accounted for and tracking of new software could be rather easy. It's still in it's pre-alpha thinking stage, so it's not really solid at the moment, but we do want something like that here to replace our currently too expensive software

                The barcode system is another module, which i came up with today. It's simple put a inventory tracking for stuff like printer cardridges (when to order new stuff) and beamers (who the hell has my beamer this time? who can we blame? >:) )

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post