Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Work towards an initial C++ theme of contributions #34

Open
rlaemmel opened this issue Jan 15, 2013 · 1 comment
Open

Work towards an initial C++ theme of contributions #34

rlaemmel opened this issue Jan 15, 2013 · 1 comment

Comments

@rlaemmel
Copy link
Collaborator

Background

We have this *.cpp stuff:

$ pwd
/home/billg/101repo/contributions
$ find . -name "*.cpp"
./cppMpl/src/cut.cpp
./cppMpl/src/total.cpp
./qt/QtImplementation/company.cpp
./qt/QtImplementation/companyobject.cpp
./qt/QtImplementation/department.cpp
./qt/QtImplementation/employee.cpp
./qt/QtImplementation/main.cpp
./qt/QtImplementation/mainwindow.cpp
./qt/QtImplementation/registry.cpp

These are the 101wiki pages for this stuff:

There are these issues:

  • Nobody has ever properly validated those contributions for general quality.
  • Most likely, these implementations are outdated in terms of the evolving feature model.
  • The documentation is either missing or incomplete.
  • The metamodel for documentation has changed anyhow and so any existing doc needs revision and extension.
  • The choice of C++ styles and technologies is somewhat arbitrary. The C++ eco system should be represented better.

Plan of action

  • Use Java- and Haskell-based implementations for inspiration, as they be of reasonable quality.
  • Understand the existing two contributions.
  • Potentially revise the existing contributions to become more "compliant" with the current feature model.
  • Provide proper documentation on 101wiki for the existing contributions.
  • Identify a few more low-hanging fruits as to what deserves coverage for C++.
  • Implement those 2 or more C++-based contributions.
  • Try to gather and use C++ best practices with regard to build and test.
  • Provide feedback to the team on what the issues where with all of the above.

Links

@ghost ghost assigned notorioussphinx Jan 24, 2013
@rlaemmel
Copy link
Collaborator Author

Ok, I sort of improved the description of the issue.
It is now also assigned to Baharak.
So we are ready to go on this one.
Have fun.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants