text stringlengths 7 369 |
|---|
[684.08 --> 686.66] I've been using Paperless-NG. |
[687.30 --> 689.46] I think it stood for Paperless Next Gen. |
[689.94 --> 691.46] Not entirely sure, to be honest. |
[692.00 --> 694.18] I like to think the next generation. |
[694.68 --> 696.02] Yeah, like make it so. |
[696.98 --> 697.88] You got it. |
[697.88 --> 701.34] A chap called Jonas Winkler |
[701.34 --> 703.86] actually took over the original Paperless project, |
[703.86 --> 705.36] which itself had been abandoned. |
[706.08 --> 707.62] Now, in the last few weeks, |
[707.86 --> 709.62] there's been a new project come along |
[709.62 --> 712.30] called Paperless-NGX. |
[712.74 --> 714.36] Next Generation X? |
[715.22 --> 716.50] Something like that? |
[717.18 --> 719.36] And essentially what the community have done |
[719.36 --> 722.56] is the NG fork of the original code |
[722.56 --> 724.36] has seemed to go unmaintained. |
[724.46 --> 725.36] There's actually a GitHub issue, |
[725.46 --> 726.62] which we'll link to in the show notes, |
[726.62 --> 729.06] where there's a bunch of people talking about |
[729.06 --> 730.74] how much value they get from the software |
[730.74 --> 732.74] and also how much of a shame it is |
[732.74 --> 733.86] to see it kind of go to waste. |
[734.44 --> 736.32] But obviously, open source being open source, |
[736.66 --> 738.58] you know, this discussion thread went on |
[738.58 --> 741.20] for, you know, the best part of two, three weeks |
[741.20 --> 743.58] before eventually the community just went, |
[744.02 --> 745.44] okay, this Jonas guy, |
[745.68 --> 748.06] he seems to have fallen off the radar for now |
[748.06 --> 748.92] for whatever reason. |
[749.40 --> 750.54] So we're just going to fork this thing |
[750.54 --> 751.48] and call it NGX. |
[752.32 --> 753.44] Yeah, I sure hope he's okay. |
[753.44 --> 755.38] You know, I hope it's just a case of burnout. |
[756.60 --> 758.76] And it is good to see something like this. |
[758.76 --> 760.38] You wouldn't, this wouldn't happen |
[760.38 --> 762.50] with a commercial service, right? |
[762.54 --> 764.42] When a cloud company is shutting down |
[764.42 --> 765.20] for whatever reason, |
[765.60 --> 767.16] the product's just kind of gone. |
[767.50 --> 768.82] But when you have something |
[768.82 --> 770.12] that you can self-host, |
[770.38 --> 771.80] that's open source software, |
[772.34 --> 775.56] there can be a escape hatch |
[775.56 --> 777.76] when the project kind of starts to fade. |
[778.08 --> 779.90] Now, this first version doesn't seem |
[779.90 --> 781.92] like it's introduced a ton of new stuff. |
[781.92 --> 784.92] They dropped support for Python 3.7. |
[785.02 --> 786.06] So they're kind of moving that forward. |
[786.18 --> 787.50] They've updated a ton of the docs |
[787.50 --> 788.94] and the scripts and the containers |
[788.94 --> 789.82] and the branding. |
[790.38 --> 791.68] They also had to drop support |
[791.68 --> 792.70] for Ansible playbooks, |
[792.74 --> 794.30] which is definitely a bummer to see that. |
[794.66 --> 796.42] But they are hoping maybe somebody |
[796.42 --> 798.34] would want to help them support that. |
[798.62 --> 800.04] It seems like maybe it's just |
[800.04 --> 802.16] an issue of things getting out of date |
[802.16 --> 804.14] and the dev team not really having |
[804.14 --> 805.38] the skill set to manage it. |
[806.16 --> 807.80] So long as they continue to support Docker, |
[808.18 --> 809.66] you know, they've got my vote. |
[809.66 --> 811.06] But what's interesting, though, |
[811.08 --> 813.66] is if we look through the issues |
[814.28 --> 814.96] on their GitHub, |
[815.24 --> 817.64] there is one specifically talking around |
[817.64 --> 821.18] moving the organization in GitHub forward. |
[821.90 --> 823.48] And, you know, so right now |
[823.48 --> 824.52] is probably a really good time |
[824.52 --> 825.64] to get involved in the project |
[825.64 --> 826.56] if you're looking to do |
[826.56 --> 828.70] any kind of open source contributions. |
[829.70 --> 830.70] You know, clearly they're looking |
[830.70 --> 832.58] to improve the project. |
[833.38 --> 835.76] There is an issue in here, 1632, |
[835.94 --> 836.68] which again will be linked |
[836.68 --> 838.02] in the show notes where they're talking |
[838.02 --> 840.62] about how you can make |
[840.62 --> 842.56] your membership official of the project. |
[843.40 --> 845.56] It's 100% a community project |
[845.56 --> 847.78] and they will gladly welcome contributions |
[847.78 --> 849.82] from anybody, member or not. |
[850.46 --> 852.48] But, you know, if you're a member of it, |
[852.54 --> 854.92] you can start to have a bit more say |
[854.92 --> 856.92] over where the direction of the project goes |
[856.92 --> 857.60] and that kind of thing. |
[858.26 --> 858.58] Interesting. |
[859.18 --> 861.12] Yeah, I wish them the best, right? |
[861.12 --> 862.64] This is one of those projects |
[862.64 --> 866.84] that I think is probably not mentioned enough. |
[867.38 --> 868.82] If you look into it, |
[868.90 --> 869.94] it's such a no-brainer. |
[870.72 --> 873.20] I'm implementing this in the future, |
[873.68 --> 874.60] probably at the end of summer. |
[875.30 --> 876.96] I'm definitely putting this into action. |
[877.30 --> 877.82] It's amazing. |
[878.20 --> 879.34] There's just no way |
[879.34 --> 881.06] I'm going to do another year |
[881.06 --> 881.86] without this system. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.