Replace README.txt with README.md

Created on 15 November 2022, over 1 year ago
Updated 13 July 2023, 12 months ago

We could be using README.md instead of README.txt to make use of the nicer rendering via markdown.

Now that we've moved to GitLab, we should probably use Markdown instead of plain .txt files for our documentation

Follow the pattern in the README.md template → .

📌 Task
Status

Closed: won't fix

Version

3.0

Component

Documentation

Created by

🇮🇳India Nila Hyalij

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇮🇳India kavitha@specbee.com

    The patch works fine and moving it to RTBC.

  • 🇺🇸United States fkelly

    Thanks to Jay and Kavitha. Maintainers are pressed for time now but we will get to this shortly. My only question is what version(s) this should go in.

    Welcome aboard. We could use more testing on the Drupal 10 release too.

  • Status changed to Needs work about 1 year ago
  • 🇺🇸United States fkelly

    Had time to look thru the patch and am moving it back to needs work.

    There are several references to "http:" instead of "https:" in the patch. Lines 4 and 14. These should be changed to https:

    The maintainers at lines 56 and lines 57 should be changed to the current active maintainers:
    Luke.Leber https://www.drupal.org/u/lukeleber →
    and
    Frank Kelly https://www.drupal.org/u/fkelly12054gmail.com →

  • 🇺🇸United States fkelly

    Just a quick note. I took at look at readme.txt in 4.0... version. Whatever is done in 8.x needs to be done in 4.x ... Not sure if separate patches are needed but we should make these versions consistent.

    Also, I'm not sure if we should keep the last couple of lines in the patch listing maintainers. Maintainers can change over time. We don't want to have to be re-patching the patch, I don't think. Even determining who is an "active" maintainer can be a bit subjective. I'm not sure if there is a standard for readme files on this. Unless there is I'd suggest just leaving it out.

  • Status changed to Needs review about 1 year ago
  • Open on Drupal.org →
    Core: 10.1.x + Environment: PHP 8.1 & MySQL 8
    last update about 1 year ago
    Waiting for branch to pass
  • Hello Everyone !!
    Created a patch for juicebox 8.x-3.x-dev. addressed#12.
    Can someone please review the patch.

    Thank you for your support!!!

  • 🇺🇸United States fkelly

    Our Senior Maintainer, Luke Leber, is the person who got the tests to pass after they had been failing for 2+ years. I'm not sure that the 8.x-3.x release has all (or any) of the changes needed to make the tests pass. Luke also modified the Drupal ci.yml file to accommodate Juicebox requirements to have a Javascript library loaded.

    When he gets a chance he can enlighten us on this. I'm not sure tests are really required for a patch such as this.

    I'm also not sure how "far back" we want to go in patching older versions of Juicebox. 8.x-3.0-alpha is identical to 8.x-3-x dev and should be used if you are "stuck" on Drupal 8 or 9 for the time being. 4.0.0-alpha1 is for sites migrating to Drupal 10 (but also should work for 8 or 9). It works with 9.3 and Drupal 10.

    I would prioritize patching the 4.0 series and getting to a stable release that support 9.3+ and all releases of Drupal 10.

  • Status changed to RTBC 12 months ago
  • 🇮🇳India kavitha@specbee.com

    Moving it to RTBC as the patch works fine.

  • Status changed to Closed: won't fix 12 months ago
  • 🇺🇸United States fkelly

    Sorry. Subject to being overruled by our senior maintainer, I am marking this as "closed, won't fix".

    Due mainly to time constraints and several years of technical debt piled up by there being no active maintainership on the Juicebox project for more than 2 years, we have our hands full getting a full set of patches working for a stable version of Juicebox for Drupal 10. Diverting attention to fixing Juicebox for Drupal 8 or Drupal 9 versions is not what we are aiming for. The Drupal 8 version 8.x-3.0-alpha2 has been working just fine functionally for 2+ years. Changing a readme file won't change or "improve" that.

    We will try to get the readme file improvements in to the stable version of Juicebox for Drupal 10 we release, once we deal with all pending functional issues: such as, just for instance, that JuiceboxFormatter.php patches that fix a dependency injection issue also cause the program to not work.

  • 🇳🇴Norway gisle Norway

    kavitha@specbee.com is owed no thanks for the "reviews" posted here.

    Before an issue can be marked RTBC the changes need to be reviewed, this wasn't done.

    kavitha@specbee.com needs to read up on Issue Etiquette → . Pay attention on #11 and #14 on the "Don't" list.

    The "reviews" posted here by kavitha@specbee.com are spam.

  • 🇺🇸United States fkelly

    Thanks @Gisle. Your support is much appreciated.

Production build 0.69.0 2024