Changes between Version 2 and Version 3 of ProjectDmdxPage


Ignore:
Timestamp:
10/04/17 19:29:43 (7 years ago)
Author:
Chichakovska Katerina
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjectDmdxPage

    v2 v3  
    99
    1010**URL:** ​
     11
    1112[1] http://www.u.arizona.edu/~kforster/dmdx/dmdx.htm
    1213
    13     [2] http://www.iub.edu/~psyling/resources/dmdx-tutorial_id_2010.pdf
     14[2] http://www.iub.edu/~psyling/resources/dmdx-tutorial_id_2010.pdf
    1415
    1516
     
    1920**Community**
    2021
     22DMDX is a member of the DMASTR family, and represents an extension of the original DOS programs (DM and DMTG) to a Windows 95/98 environment.
     23
    2124**Leadership**
     25
     26Jonathan Forster
    2227
    2328**Forking**
    2429
     30You can create your own fork of the central repository. First go to github, create an account and make a fork of the DMDX repository. You can change your fork in any way you choose without it affecting the central project. You can also share your fork with others, including the central project.
     31
    2532**Communication**
     33
     34All users of DMDX are encouraged to subscribe to the list.  If you have a problem, post it, and somebody will answer. First you must sing up. Send a message to list@list.arizona.edu from the address you want to subscribe to the list.Once your subscription is confirmed posts can be made to dmdx@list.arizona.edu.
    2635
    2736**Roadmaps**
    2837
     38TBD
     39
    2940**Releases**
     41
     42TBD
    3043
    3144**Repositories**
    3245
     46The use of git allows people to contribute changes that can easily be incorporated back into the project, while maintaining order and consistency in the code. All changes should be tracked and reversible.
     47
    3348**Packaging**
     49
     50TBD
    3451
    3552**Upstream/downstream**
    3653
     54Only a couple of people have direct write-access to the DMDX repository, but you can get your changes included in upstream by pushing your changes back to your github fork and then submitting a pull request.
     55
    3756**Version Control**
     57
     58The last Update was on 21 May 2017.
    3859
    3960**Trackers**
    4061
     62You can track the changes on the folowing link: http://www.u.arizona.edu/~jforster/dmdx.htm
     63
    4164**Project Evaluation**
    4265
     66The first step of founding DMDX was May 1997. After that DMDX is constantly developed.
    4367
    4468== **Fieldtrips**==
     
    4771**Github:**
    4872
     73[1] https://github.com/txipi/VisualDMDX
     74
    4975**Openhub:**
     76
     77TBD
    5078
    5179**Source Forge:**
    5280
     81TBD
     82
    5383== **Evaluation** ==
    5484
    55 **Licensing** GNU General Public License v3.0
     85**Licensing**
     86
     87GNU General Public License v3.0
    5688
    5789**Language**
    5890
     91!JavaScript
     92
    5993**Activity**
     94
     95Active
    6096
    6197**Number of contributors**
    6298
     99It has many contributors such as: John Allen, Jeff Bowers, Matthew Chung, Matt Davis, Zia Dikman, Mike Ford, Gareth Gaskell,  Michael Johnston, Ralph Mertens, Dennis Norris, Mary Peterson, David Schnyer etc.
     100
    63101**Size**
     102
     103TBD
    64104
    65105**Issue tracker**
    66106
     107It has forum on which you can ask your question.
     108
    67109**New contributor**
     110
     111On the !GitHub provides a straightforward way for collaborating on a project.
    68112
    69113**Community norms**
    70114
     115You can create a fork of the central DMDX repository. You can also create a local clone of that fork: for small changes(make the changes directly in the master branch, push back to your fork, submit a pull request to the central repository) and for substantial changes (create a branch, when finished run unit tests, when the unit tests pass merge changes back into the master branch, submit a pull request to the central repository).
     116
    71117**User base**
     118
     119It has its own strong user base.