During the last year Askbot, a question and answer oriented internet tool, similar to stack overflow has been tested for internal usage.

The testing went well and it was decided to use the tool in a larger scope.

Trying to prepare the tool for this we found that the source code under https://github.com/ASKBOT/askbot-devel is still Python 2 and not well maintained. As it is not even compatible with current openSUSE Leap 15 and we don't want to run it in some insecure not updatable container we decided after a short discussion that:

  1. Askbot would still be a very valuable tool for SUSE

  2. We want to have it

  3. The best solution to get this done is to port Askbot to Python 3

Aim of this Hackweek project would be to port Askbot to Python 3.

See https://github.com/ASKBOT/askbot-devel/issues/772

Update!

Good news: We're getting help from upstream!

Looking for hackers with the skills:

python django

This project is part of:

Hack Week 18

Activity

  • over 6 years ago: aspiers liked this project.
  • over 6 years ago: itxaka liked this project.
  • over 6 years ago: ssebastianwagner added keyword "python" to this project.
  • over 6 years ago: ssebastianwagner added keyword "django" to this project.
  • over 6 years ago: rsimai liked this project.
  • over 6 years ago: rsimai disliked this project.
  • over 6 years ago: rsimai liked this project.
  • over 6 years ago: ssebastianwagner started this project.
  • over 6 years ago: rbueker liked this project.
  • over 6 years ago: rbueker originated this project.

  • Comments

    • ssebastianwagner
      over 6 years ago by ssebastianwagner | Reply

      I've just joined #askbot on freenode IRC to coordinate things

    • ssebastianwagner
      over 6 years ago by ssebastianwagner | Reply

      Update: Askbot in our fork is running on Python 3!

    Similar Projects

    Bring to Cockpit + System Roles capabilities from YAST by miguelpc

    Bring to Cockpit + System Roles features from YAST

    Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.

    Goals

    The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.

    Resources

    A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit

    Linux System Roles: https://linux-system-roles.github.io/