Open Source Ecology - User contributions [en]

Pizzooid Log

2021-04-15T10:54:16Z

Pizzooid:

== Thu, Apr 15, 2021 ==
First working container on [https://hub.docker.com/repository/docker/palmesi/ose-2.0/ Docker Hub]

== Mon, Apr 11, 2021 ==
Updated [https://github.com/pizzooid/ose-docker Docker repo]
Created container on [https://quay.io/repository/ose/ose-docker quay.io]

== Sat, Apr 3, 2021 ==
[https://askubuntu.com/questions/9135/how-to-backup-settings-and-list-of-installed-packages How to backup the list of installed packages]

[https://github.com/pizzooid/ose-docker/tree/main Start Docker Repo]

== Wed Feb 17, 2021 ==
[[Talk:Wiki Log]]
== Sun Feb 14, 2021 ==
[[OSE Linux]]
== Sat Feb 13, 2021 ==
[[Talk:OSE Linux Docker]], [[Talk:The Case for Using Wiki Version History#Continued Argumentation]]

== Wed Feb 10, 2021 ==
Setup [[OSE Linux]] USB Drive.

== Sat Feb 6, 2021 ==
[[Talk:The Case for Using Wiki Version History]]

Pizzooid Log

2021-04-12T18:49:09Z

Pizzooid:

== Mon, Apr 11, 2021 ==
Updated [https://github.com/pizzooid/ose-docker Docker repo]
Created container on [https://quay.io/repository/ose/ose-docker quay.io]

== Sat, Apr 3, 2021 ==
[https://askubuntu.com/questions/9135/how-to-backup-settings-and-list-of-installed-packages How to backup the list of installed packages]

[https://github.com/pizzooid/ose-docker/tree/main Start Docker Repo]

== Wed Feb 17, 2021 ==
[[Talk:Wiki Log]]
== Sun Feb 14, 2021 ==
[[OSE Linux]]
== Sat Feb 13, 2021 ==
[[Talk:OSE Linux Docker]], [[Talk:The Case for Using Wiki Version History#Continued Argumentation]]

== Wed Feb 10, 2021 ==
Setup [[OSE Linux]] USB Drive.

== Sat Feb 6, 2021 ==
[[Talk:The Case for Using Wiki Version History]]

Pizzooid Log

2021-04-03T15:09:23Z

Pizzooid: /* Sat, Apr 3, 2021 */

== Sat, Apr 3, 2021 ==
[https://askubuntu.com/questions/9135/how-to-backup-settings-and-list-of-installed-packages How to backup the list of installed packages]

[https://github.com/pizzooid/ose-docker/tree/main Start Docker Repo]

== Wed Feb 17, 2021 ==
[[Talk:Wiki Log]]
== Sun Feb 14, 2021 ==
[[OSE Linux]]
== Sat Feb 13, 2021 ==
[[Talk:OSE Linux Docker]], [[Talk:The Case for Using Wiki Version History#Continued Argumentation]]

== Wed Feb 10, 2021 ==
Setup [[OSE Linux]] USB Drive.

== Sat Feb 6, 2021 ==
[[Talk:The Case for Using Wiki Version History]]

Pizzooid Log

2021-04-03T15:09:09Z

Pizzooid: /* Sat, Apr 3, 2021 */

== Sat, Apr 3, 2021 ==
[https://askubuntu.com/questions/9135/how-to-backup-settings-and-list-of-installed-packages How to backup the list of installed packages]
[https://github.com/pizzooid/ose-docker/tree/main Start Docker Repo]

== Wed Feb 17, 2021 ==
[[Talk:Wiki Log]]
== Sun Feb 14, 2021 ==
[[OSE Linux]]
== Sat Feb 13, 2021 ==
[[Talk:OSE Linux Docker]], [[Talk:The Case for Using Wiki Version History#Continued Argumentation]]

== Wed Feb 10, 2021 ==
Setup [[OSE Linux]] USB Drive.

== Sat Feb 6, 2021 ==
[[Talk:The Case for Using Wiki Version History]]

Pizzooid Log

2021-04-03T15:08:19Z

Pizzooid:

== Sat, Apr 3, 2021 ==
[https://askubuntu.com/questions/9135/how-to-backup-settings-and-list-of-installed-packages How to backup the list of installed packages]
== Wed Feb 17, 2021 ==
[[Talk:Wiki Log]]
== Sun Feb 14, 2021 ==
[[OSE Linux]]
== Sat Feb 13, 2021 ==
[[Talk:OSE Linux Docker]], [[Talk:The Case for Using Wiki Version History#Continued Argumentation]]

== Wed Feb 10, 2021 ==
Setup [[OSE Linux]] USB Drive.

== Sat Feb 6, 2021 ==
[[Talk:The Case for Using Wiki Version History]]

Pizzooid Log

2021-02-17T21:18:42Z

Pizzooid:

== Wed Feb 17, 2021 ==
[[Talk:Wiki Log]]
== Sun Feb 14, 2021 ==
[[OSE Linux]]
== Sat Feb 13, 2021 ==
[[Talk:OSE Linux Docker]], [[Talk:The Case for Using Wiki Version History#Continued Argumentation]]

== Wed Feb 10, 2021 ==
Setup [[OSE Linux]] USB Drive.

== Sat Feb 6, 2021 ==
[[Talk:The Case for Using Wiki Version History]]

Wiki Log

2021-02-17T21:15:32Z

Pizzooid: /* Thu Feb 4, 2021 */

This is a log of wiki issues, performance, improvements, organization, and other issues related to the effective functioning of the wiki. See [[OSE Wiki Bugs]] and [[Wiki Issues]].

Other pages to see:
*[[Wiki Maintenance]]
*[[OSE Wiki Management]]
*[[OSE Wiki]]

=Sun Feb 7, 2021=
<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000#3" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.gbb9a4d6c30_0_0 edit]

=Thu Feb 4, 2021=

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000#2" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

Trying to reproduce the error on [[File:VersionBug.fcstd]]

[[User:Pizzooid]] was not able to reproduce the error:
Steps tried to reproduce:

# Upload version
# Download version
# Upload new version
# Download new version

the new version is correctly downloaded on my computer. Is this different on your end?

View discussion at [[Talk:Wiki_Log#Discussion_Thu_Feb_4.2C_2021]]

=Sat Oct 17, 2020=
Saving SVGs doesn't work -

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

=Thu Dec 27, 2018=
*Check out this interesting bug - the picture is not updating when new version of a picture is uploaded. The next to last picture is the latest one - but the image that shows up shows the older picture:

[[File:noupdate.png|400px]]

=Wed May 23, 2018=
*Mass Delete in special pages - for mass delete of spam by one user
*Use the User:Name and Tools: email this user to contact users

=Thu Feb 2, 2017=
==Wiki Outstanding Items==
*Get proper sidebar on new wiki
*Speed up wiki response
*Get main page up
*Approve users manually
*Learn how to navigate between instructionals view and regular wiki view
*After all formatting is done - first update database for last time - and swith DNS record at Dreamhost

==Main OSE blog, Factor e Farm, Opensourcewarehouse.org, old Forum==
*Other databases have different logins - fef wp site, opensourcewarehouse wp, old forum in vanilla
*wp-config.php has the password info to find other databases -
*localsettings.php has initial settings for wiki software. We had that password already. Read only vs. write only login was shown.

We got so far as to getting the database for the fef site, by extracting password from the wp-config. We copied to new Hetzner. We archived also the entire fef wordpress database file and working directory into one archive and moved it to the new Hetzner.

Next steps are to move main ose wordpress, and the opensourcewarehouse.org wp database. And finally look up old forum database password, and then move that.

Ok. Bye.

Let's fix up the new Hetzner - how to make it look good.

=Tue Feb 23, 2016=
Changing license information at bottom of page from 3 to 4:

Marcin;

1. Log onto the server via ssh (assuming that you have the hetzner key in your .ssh folder, named as shown below):
$ ssh -i ~/.ssh/id_rsa-hetzner -p 222 -l osemain dedi978.your-server.de

2. Change to the "public_html/w" folder and edit the file "LocalSettings.php":
osemain@dedi978:~ cd public_html/w
osemain@dedi978:~$ nano LocalSettings.php
3. Change the text from 3.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/3.0/";
$wgRightsText = "CreativeCommons by-sa3.0";
to 4.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/4.0/";
$wgRightsText = "CreativeCommons by-sa4.0";
I just changed it for you using the steps above.

=Wed Dec 3, 2015=
Need to enable email capture from wiki registrations. Currently, the email is lost after registration is approved.

=Mon Sep 21, 2015=
Larger than 50MB files can't be uploaded still - trying the [[Cold Saw]] zipped CAD file upload.

=Thu Sep 10, 2015=
Marcin;

It appears to delete all attachments after the user account is confirmed, by an automated maintenance script.

In the database, it holds a record of the file while the account is pending, but afterward, there is nothing about it in the database.

I haven't found where it keeps the files meanwhile. It appears to encrypt the file name, as I see two values for its name, but not the file itself:
82a8f59a58588754c6ac4a8016c581ee3d37703f.pdf
and
150622_CV_EN.pdf
The weird thing is that when I click on the file name "150622_CV_EN.pdf", it somehow finds it. Weird.

Tom

=Thu Sep 3, 2015=
Example - http://opensourceecology.org/wiki/User:Pcharwood - upon registration, his resume - I clicked on it - and got it. But the second time I clicked on it, it was a bad link - http://opensourceecology.org/w/index.php?title=Special:ConfirmAccounts/authors&file=01ef55cbe8049485974417e742b372eeb73612df.pdf .

=Sat Aug 29, 2015=
Account registration fields - where to find them? When a person registers, there are other fields filled in, such as contact info. How to find this once a user is approved? Further, the uploaded CV - when clicked upon - it was a broken link but link was blue. Status: not resolved.

=Sat Aug 22, 2015=
Are [[Terms of Service]] visible upon a person registering? This refers to a Contributor Agreement. With this said - how do we find a person's profile and CV that they submit upon registration? That is critical to Wiki Culture and Collaborative Literacy. Status: not resolved

=Fri Aug 14, 2015=
Had an error - [[Image:wikierror.png|thumb]] - and Tom fixed it. He set the upload directory to the same as the photo upload directory. BTW: This setting is made in the file: /usr/home/osemain/public_html/w/includes/DefaultSettings.php. "I also document my changes in the file with the original lines intact so they can easily be returned to original settings."

[[Category:Logs]]

Talk:Wiki Log

2021-02-17T21:14:08Z

Pizzooid: /* Discussion Thu Feb 4, 2021 */ new section

== Discussion Thu Feb 4, 2021 ==

If the problem persists after trying CTRL-F5 as suggested in [https://www.mediawiki.org/w/index.php?title=Topic:Udaydwejo96temng&topic_showPostId=v9nhi7k7aojn0a5h#flow-post-v9nhi7k7aojn0a5h]
you could try another thing:

when downloading the file you can copy the link and then add a dummy variable to the link so the browser thinks it is a different file like so:
* If I am on the page https://wiki.opensourceecology.org/wiki/File:VersionBug.fcstd
* I can right-click on the latest version and copy the following link: https://wiki.opensourceecology.org/images/c/c9/VersionBug.fcstd
* I can now modify the link by adding any variable to the end of the address like so: https://wiki.opensourceecology.org/images/c/c9/VersionBug.fcstd?a=true
* this would trick my browser into downloading the same file from a different address.
But if the problem only appears locally, why would you want to download the file you just uploaded?

Talk:Wiki Log

2021-02-17T21:05:38Z

Pizzooid: Blanked the page

Talk:Wiki Log

2021-02-17T21:05:24Z

Pizzooid: Created page with "= Discussion Thu Feb 4, 2021 ="

= Discussion Thu Feb 4, 2021 =

File:VersionBug.fcstd

2021-02-17T20:48:53Z

Pizzooid:

Try to create a new link to the current version:
[[Media:VersionBug.fcstd&oldid=244158]]

File:VersionBug.fcstd

2021-02-17T20:48:37Z

Pizzooid:

Try to create a new link to the current version:
[Media:VersionBug.fcstd&oldid=244158]

Talk:The Case for Using Wiki Version History

2021-02-17T20:42:51Z

Pizzooid: /* Continued Argumentation */

=Meta-Discussion=
Major advantages on git - what are those advantages? What problem are we trying to solve?

Once we are clear on advantages, and problem we are solving - we have an answer.

The first question for you - what are those advantages of Git that our workflow can benefit from? What problem is a Git platform solving that is important to us, that is not addressed by the wiki versioning?

==Major Advantages==
#'''Support''' MediaWiki’s major target is Wikipedia. Wikipedia was not intended to be used as a development environment but rather as an encyclopedia. Support and for using it as a version control system is likely going to be limited.
#'''Robustness''' - Git is well tested as a versioning system vs not many people use MediaWiki as a versioning tool.
#'''Data Replication''' - With git every collaborator has a copy of the file, they could work even when the server is down. Should a problem with the server happen, every collaborator has a backup.
#'''Versions have a hash key''' - In Git every commit has a unique hash key it can be referred to. A version can always be linked to by its unique hash - In Wikipedia on the other hand there is only a timestamp and the current version <strike>changes</strike> retains its link after a new version is added. Old versions can be accessed directly via their unique link.
#'''Extensibility/Automation''' - Git servers usually have the ability to do certain tasks when a new version is uploaded. A continuous integration server can automatically check files for correctness and create preview images.
#'''Access Control''' - In git, a part of the developers can be maintainers that first have to check changes before they make it into the official version.
#'''Accidental Overwrites'''- In Wikipedia two people could submit a file at the same moment and not see that another person did the same, one of the commits would be overwritten - Git prohibits this behavior. That said, I can see that WikiMedia might just be good enough for now but I would also be open to doing a few demos on how git could be used as an alternative.

'''Is any one of the reasons important enough?'''

==Counterarguments on Major Advantages==

#'''Support''' - Wikipedia has a version control system, so in that sense it ''supports'' file versioning. Our requirement is ''keep all files from all contributors easily accessible, time stamped, and downloadable at any time without risk of data loss and without merge conflicts - while requiring only widely-accessible skill levels for team coordination.''' I think mediawiki does a better job at this problem statement, because you can see all the people working on the issue readily in the history. Further, our use of [[Visual Version History]] and CAD Part Libraries allows for quick visual diffs, where ready visual diffs would be much more difficult as they would be sread throughout many developers' accounts until they are committed to master. Navigating version histories is readily accessible to novices, whereas Github is pretty much for power users.
#'''Robustness''' - Counterargument: yes, robustness in software, but it is not robust for open hardware development. For example, it can't handle video. So in terms of robustness, Git is less robust for handling a more complex process of hardware dev, for an integrated process like OSE uses. But certainly it's more robust for software, and we should use Git for software.
#'''Data Replication''' - The same is effectively true for the wiki, because every collaborator has a copy of the files they are working on. I would argue that Data Replication is not possible for hardware - as for hardware, the whole project is terabytes (from videos and heavy assets such as large CAD assemblies). This is why a wiki-centric infrastructure is good. So this points to defining the problem statement clearly: Git is good for software, not for hardware. The initial qeustion is: why use wiki version history? The second question that we are asking, why use wiki for project management as opposed to git. Having specified the question, we can answer: we use wiki for overall development, we use git for software only, as a general best practice.
#'''Versions have a hash Key''' - wiki has the equivalent functionality of a hash key.
#'''Access control''' - The [[GVCS]] (creating a new infrastructure for civilization) is a broader project, therefor we allow everybody in without the need for a access control. The only question is spam, which we address by manual approval of new users.
#'''Accidental Overwrites'''- I'm not aware that this is an issue. If there is a submission conflict, that is clear to the submitter - their upload fails, and they upload a file again. If 100 people do this, they just try again and the upload should be reconciled in seconds. But there is never typically a large number of people working on a single file, as we normally coordinate so that if there are multiple people working, we work on different files, or break the file into smaller parts for multiple people to work on them. Further, we also encourage people to use their work log as a repo, and add to the main trunk at a later date. Accidental overwrite can be an issue for page edits - but not for file uploads. For page edits, we use embedded documents, which are crowd-collaborative-realtime-editable and never suffer from 'submit' conflicts.

==Continued Argumentation==
#'''Versions have a hash Key''' - wiki has the equivalent functionality of a hash key.
## I don't think that this is true. The problem with the wiki is that the latest version does not really have a hash, older versions can be linked to, but the newest version always has the same link, there is no permanent link. Or is there a way to address the current link for the future?
### Ok, so the hash-key functionality is actually the permalink functionality, sadly it only links to the Wikipage of the file but not to the file itself.

=Discussion=

I agree that given that you are using a wiki as a repository you would want to just upload a new version of a file and use it. I just think that MediaWiki was not intended to be used as a repository.

If I understand correctly the reason you gave for not using Git are

# You don't control the data with Gitlab
# Visual Version History
# Collaboration on a scale
# It is currently used for a large set of parts (this was not included originally but I think it is important)

I still think Git has major advantages and want to give counterpoints to the arguments above

== 1. You don't control the data with Gitlab ==

Q: I don't understand this, why don't you own the data, you can host it on your server.

A: Then why not just use our server? This means that we're hosting the data in 2 places, so why not just host it on our servers? And if Gitlab decides to end service, we have to have a local backup. Or if it changes its interface or usage terms, we may have to rework significant parts of our workflow. We need absolute control of our data as we are a long-term project.

== 2. Visual Version History ==

Q. I think that Visual Version History should not be a problem, you can either just continue using the wiki and then link to the git files. Even better, the visual version history could be automatically created as a commit hook and on GitLab.

A. Could be created: a visual gallery like in the wiki, but it already exists in Mediawiki so why reinvent the wheel? The wiki already has all the formatting to make this easy. And we don't want to require people understanding how to use Git platforms, which is a higher learning curve than a wiki.

== 3. Collaboration at a scale ==

Q: I think there is a case that the access privileges are much better with Git. I believe that pull requests are probably necessary on a very large scale collaboration.

A: That is specific to software workflows. In hardware workflows, authority is more distributed. The builder has ultimate authority. A software platform of Git relies on commits and commit control. A hardware platform needs to rely on 'non-commits'. I mean that every design is valid until it is tested. Because there is no uniform compiler in hardware, or it is more expensive to 'compile' or build - much work by default remains non-reconciled or 'un-committed' - as a potential viable fork. So in summary, hardware by its nature requires no access privileges - as decision-making (on commits or reconciliatiuon) is much more distributed in hardware. Ie, the guy in Africa, North Pole, Europe, and rural american town all need equal access - and whoever builds, decides. So permissions are simple: all source is open, and any build is an effective fork. So it seems that the workflow from software is the general idea, but in practice - the practices are subtly different. Specifically: you don't need access privileges - default is all open and the builder is the actual committer. You can't assign roles and privileges in hardware - it doesn't make sense.

== 4. It is currently used for a large set of parts ==

Q: I think this point is very strong and that the transition could be a lot of work. But I still think that it could be worth it, and it should be tried out.

A: Qeustion 3 implies that the problem statement is not reconciliation (commits). It's more about who puts up the effort to build. Yes, we can all collaborate on digital design and treat it like software - ie, someone takes the control of commits. Because you cannot pre-allocate the commit-control role, you cannot scale in the same way in hardware as in software.

Pizzooid Log

2021-02-14T21:17:23Z

Pizzooid:

== Sun Feb 14, 2021==
[[OSE Linux]]
== Sat Feb 13, 2021==
[[Talk:OSE Linux Docker]], [[Talk:The Case for Using Wiki Version History#Continued Argumentation]]

== Wed Feb 10, 2021 ==
Setup [[OSE Linux]] USB Drive.

== Sat Feb 6, 2021 ==
[[Talk:The Case for Using Wiki Version History]]

OSE Linux - 2.0 version from 2020

2021-02-14T21:16:41Z

Pizzooid: Add Instruction on how to create a docker container from an image

{{Hint|'''OSE Linux 2.0 is coming out at the end of August - try a preview - https://www.caldorkids.com/ose/}}

{{Hint|You are welcome to download OSE Linux and make a live USB. We can also send you a USB stick withe the live OSE Linux distribution. To receive a copy by mail, please send $10 through our <html>
<form action="https://www.paypal.com/cgi-bin/webscr" method="post" target="_top">
<input type="hidden" name="cmd" value="_s-xclick" />
<input type="hidden" name="hosted_button_id" value="5XFQZM7X9B3JE" />
<input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif" border="0" name="submit" title="PayPal - The safer, easier way to pay online!" alt="Donate with PayPal button" />
<img alt="" border="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif" width="1" height="1" />
</form>

</html> button, and include your address when you go through PayPal. You can also send us a check. See [[Donate]] page for more options, or email info at opensourceecology dot org.}}

=What is It?=

[[Image:oselinux.jpg|thumb|OSE software stack.]]

'''OSE Linux''' is a freely downloadable operating system that contains all software that is used regularly at OSE. It is run as a [[Live USB]] without the user having to modify or upset their usual operating system in any way whatsoever. This provides access to exactly the same software that we use during workshops and other training sessions - to avoid differences in versions common to different operating systems. During our training sessions, we will use OSE Linux ourselves - so your programs will look exactly like ours. This addresses hours of potentially wasted time due to differences in software or software not working.

OSE Linux also addresses the tens of hours that it would potentially take to download and configure all the software and libraries in common use by OSE. Instead, a single install, taking under half hour of dedicated user time after download, is sufficient to download the entire operating system. This is useful in large-scale collaborative processes - where everyone should use the exact same system to promote a seamless experience.

It is a good practice for [[OSE Developers]] to download and use the system to avoid software malfunction, improper settings, and in general the time it takes to download or install various software and its extensions, such as additional workbenches in FreeCAD, browser plugins, etc. OSE uses only open source software to produce all of its work product to facilitate interoperability with a large global team of developers.

'''Please note that OSE uses a lot of custom software - so please save yourself hours of install time and and just download the prepared OSE Linux. We are doing this to make your life easy. Note also that you should not run OSE Linux in a Virtual Machine, as a Virtual Machine will be much slower at computation intensive tasks such as CAD.'''

OSE Linux can be used by downloading the ISO, and creating a bootable USB stick. Instead of using one's regular operating system, one can choose - upon startup - to run the OSE Linux operating system from a USB stick, without installing it on one's hard drive. '''Note that currently you can't save files on the Live Linux - so upload any documents to your log, the wiki, or use cloud-documents where data is not saved locally.'''

==OSE Linux at Workshops==
For reasons of software uniformity, we like to use OSE Linux. Our experience with prior workshops at OSE which involve software training was that always there was someone who could not run some software properly, or there would be some differences in the software on different platforms. This typically obstructed smooth progress of everyone following along during software training. For this reason, we like to use OSE Linux live, so that everyone has the exact same copy. All that people need to do is to boot from our USB. Once booted, uniform results are pretty much guaranteed. Thus, we begun using OSE Linux in 2017 as a regular practice during OSE workshops - where participants are instructed to either make their own USB at home - or we provide the USB at the OSE site.

=OSE Linux v2.0=

'''Download the 7.2G file at: https://www.caldorkids.com/ose/

See [[OSE Linux v2 Notes]]
==Software List==
This is a list of software on OSE Linux 2. The selection of software is evolving for the needs of regenerative solutions at scale.

<html><iframe src="https://docs.google.com/spreadsheets/d/1hk1Tec4tkEDe47sEtRu7wySa8U4zYWBEat_dWZezQa0/pubhtml?widget=true&headers=false" height=500 width=800></iframe></html>

[https://docs.google.com/spreadsheets/d/1hk1Tec4tkEDe47sEtRu7wySa8U4zYWBEat_dWZezQa0/ edit]

==Software Notes==
*[[OSE Linux 2 Software Notes]]
*Mixxx - digital DJ platform to [[Twitch]]

=Download and Install OSE Linux Live ISO=
Requirements: ISO image, 4 GB USB stick
==v1.0 from 2017==

Download the [https://en.wikipedia.org/wiki/ISO_image .ISO Image] file below. This will then be installed onto a USB flash drive to create a [https://en.wikipedia.org/wiki/Live_USB Live USB].

* [https://archive.org/details/OSELinux1.0 Internet Archive]
* [https://archive.org/details/OSELinux1.0 Torrent]
* [magnet:?xt=urn:btih:1b86fa4bdccea4308a115f7f0dbe9eeb93f37fe2&dn=OSELinux1.0&tr=http%3a%2f%2fbt1.archive.org%3a6969%2fannounce&tr=http%3a%2f%2fbt2.archive.org%3a6969%2fannounce&ws=http%3a%2f%2fia601504.us.archive.org%2f24%2fitems%2f&ws=http%3a%2f%2fia801504.us.archive.org%2f24%2fitems%2f&ws=https%3a%2f%2fia801504.us.archive.org%2f24%2fitems%2f Magnet Link]

==How To Create an OSE Linux USB using Ubunutu==

Objective: A bootable USB stick that provides the OSE Live desktop, and will run all the OSE programs without touching any existing locally installed OS on the computer.
It's a way to test, and use, the OSE programs (3D design, 2D design, video capture and edit, resource management) and not disturb the current computer setup.

1. Download the ISO (See above for current ISO URL) <br />
2. Burn ISO to USB<br />
For Setting up the USB stick, follow the instructions [[How_to:Write_Image_to_SD_Card]], <br>
simply swap the word SD for USB. There are no customizations to be made as they are suggested at the bottom, all is working out of the box.

3. Boot your computer with the USB. See [[OSE Linux#Getting Started]]

<br><br><br><br>
'''Here is the video HowTo for Ubuntu 16.04 users, GUI version'''<br>
<html><video height="400" controls>
<source src="https://wiki.opensourceecology.org/images/2/23/OSE_Live_USB_HowTo.webm" type="video/webm">
Your browser does not support the video tag.
</video></html>

http://opensourceecology.org/w/images/2/23/OSE_Live_USB_HowTo.webm

<html><iframe src="https://docs.google.com/document/d/1w2kDCAVJSsMwQuX4gstq-YLM0X2l32H6cTlbD2zwJM4/pub?embedded=true" height=400 width=80%></iframe></html>

[https://docs.google.com/document/d/1w2kDCAVJSsMwQuX4gstq-YLM0X2l32H6cTlbD2zwJM4/ edit]

===Creating an OSE docker container===
Tutorial for creating a docker container from an image: [https://www.techrepublic.com/article/how-to-convert-an-iso-to-a-docker-image/]

==How To Create an OSE Linux USB using Windows==

[https://rufus.akeo.ie/#download Download Rufus]

<html><iframe src="https://docs.google.com/document/d/1baJdLIh1m7_VjUoDq2-9P1LWRzwUcQkxhl0ZNB_6WoU/pub?embedded=true" height=400 width=80%></iframe></html>

[https://docs.google.com/document/d/1baJdLIh1m7_VjUoDq2-9P1LWRzwUcQkxhl0ZNB_6WoU/ edit]

===Setting up the OSE_OS on a Virtual Machine (using VirtualBox) on a Windows System.===
The links below would help with: '''Setting up the OSE_OS on a Virtual Machine (using VirtualBox) on a Windows System.'''<br>
Note that some lag might be experienced with such an installation depending on your system specs and some OpenGL glitches have been reported in the past though they seem currently resolved. If the ability to switch seamlessly from Ubuntu to Windows without having to reboot is essential as an option, it might be worth a try:<br>
[http://www.psychocats.net/ubuntu/virtualbox Installing Ubuntu inside Windows using VirtualBox]<br>
[https://www.howtogeek.com/howto/2845/install-guest-additions-to-windows-and-linux-vms-in-virtualbox/ Install Guest Additions to Windows and Linux VMs in VirtualBox]<br>
[https://www.howtogeek.com/187703/how-to-access-folders-on-your-host-machine-from-an-ubuntu-virtual-machine-in-virtualbox/ How to Access Folders on Your Host Machine from an Ubuntu Virtual Machine in VirtualBox]

==How To Create an OSE Linux USB using Mac==
Key Howtos:
*From Tom - [https://tutorials.ubuntu.com/tutorial/tutorial-create-a-usb-stick-on-macos#0]
*'''[https://gist.github.com/gregoryfoster/35d8037a6a8424661a8a2606c1280785 How To Create a bootable Open Source Ecology (OSE) Linux USB Stick on Mac OS X - github]'''
*[[How to Create an OSE Linux USB using Mac Guide by Alex Au 2018]]

'''Download'''

Download the latest OSE Linux ISO disk image [[OSE_Linux#Download_and_Install_OSE_Linux_Live_ISO]].

'''Insert your USB Stick and determine its device identifier'''

# Insert USB stick
# Open a Terminal window
# Determine USB stick device ID: `diskutil list`

<nowiki>

$ diskutil list
...
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: *16.0 GB disk3
</nowiki>

'''Create a bootable USB Stick from a hybrid disk image'''

Using a hybrid ISO disk image is by far the simpler approach as you just overwrite the entire USB stick.

# Unmount all partitions on device: `diskutil unmountDisk [Device ID]`
# Copy ISO: `sudo dd if=[Path to ISO] of=[Device ID] bs=1048576`
#* Press CTRL+T to send a SIGINFO signal to `dd` to track progress [http://osxdaily.com/2015/06/05/copy-iso-to-usb-drive-mac-os-x-command/#comment-1718523 source]

<nowiki>

$ diskutil unmountDisk /dev/disk3
Unmount of all volumes on disk3 was successful
$ sudo dd if=~/Downloads/ose0.3isohybrid.iso of=/dev/disk3 bs=1048576
2142+0 records in
2142+0 records out
2246049792 bytes transferred in 1841.710284 secs (1219546 bytes/sec)
</nowiki>

The partition is automatically marked as as bootable.

Eject USB Stick: `diskutil eject [Device ID]`

<nowiki>

$ diskutil eject /dev/disk3
Disk /dev/disk3 ejected
</nowiki>

And you're good to go.

=Getting Started=
'''Instructions for using OSE Linux for the first time'''

==Booting Up and BIOS Settings==

After powering on your computer, but before your normal operating system starts, you can access your boot settings.

'''Boot target computer from USB Stick'''

First, configure the BIOS to prioritize booting from a USB drive. In my case, I'm installing on an HP Spectre x360 laptop [http://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery/How-to-boot-from-USB-flash-drive-HP-Spectre-x360/td-p/5032935].

# Power up HP Spectre x360
# Press `F10` to enter the BIOS
# Navigate to System Configuration
# Select Boot Options
## Disable Secure Boot
## Enable Legacy Boot
## In UEFI Boot Order move USB Diskette to top of list
## In Legacy Boot Order move USB Diskette to top of list
## Disable 3D Graphic Acceleration
# Press `F10` to save changes and exit BIOS

Your system will restart, recognize the USB Stick, and boot its contents.

_For existing Linux systems with a boot manager installed, you may still need to intervene to select an alternative boot option. Press `F9` to enter Boot Options and choose the USB Disk._

==Software Tutorials==

*[[FreeCAD 101]]
**[[Old FreeCAD Tests]]
*[https://en.wikibooks.org/wiki/OpenSCAD_User_Manual OpenSCAD wikibook]

=Testing=

We are documenting which systems work successfully for Live boot and/or install of the OSE Linux ISO.

Please document 3 things:
#Version of the OSE Linux you are trying to boot and/or install - date or link to the download from above. Note that new versions will be published quarterly. It is impotant to keep notes on the specific version that you are using so there is no confusion on which OSE Linux versions are successful
#Hardware you are using, such as Dell Precision M6500 Laptop
#Operating system that you are using on your hardware - such as Ubuntu 16.04.

To document this for your system, please go to See [[ISO to USB Install Notes]]. The test should verify the following specific usage points, and receive "100% tested and working" condition for the ISO to be considered done (ie, for example, we cannot have the Dimension Drawing Workbench not working in FreeCAD. For the specific usage points that are marked "Not Cricital", they do not count in the grading.

#Is the time zone set correctly? (Not critical)
#[[File:check.png]] Does Chromium connect to wireless internet without a problem?
#Is the version of Arduino 1.6.8 as the default?
#Does Arduino IDE upload sample program to the Mega after selecting the correct board and port under Tools?
#Is OSE Marlin available within Arduino?
#Can you download a file from Part Library on the wiki and open it in FreeCAD?
#Does the Exploded Part Animation workbench create part explosions without crashing?
#Do files download to the desktop (so a new user can find files immediately without having to find the Downloads folder in the directory structure)?
#Can you upload files to the wiki, such as an image?

=Troubleshooting=
*[[How to Troubleshoot Wireless on OSE Linux]]

=OSE Linux Development=
'''This section is used by developers making OSE Linux'''

==How To Create the ISO File Using Ubuntu==
We are using the customizer by kamilion:
<br>
https://github.com/kamilion/customizer/wiki/First-guide
<br>
however, there is a problem with the iso creation process:
we need to modify the source code, as the kernel download will otherwise fail and disturb the creation of the iso. This has of course to be done before the compiling into a deb file. For that, we have to edit:<br>
/{Unzipped Master}/src/actions/rebuild.py
go to the line <br>
detect_boot()
and look under it, there should be a line going like <br>
if config.KERNEL is not default
comment that out (with #) until next else (including the else) and then correct the intendation (as python is very sensitive to that), meaning everything to the next empty line has to be moved left one 4 whitespaces. In the end, it should look like this:
#if config.KERNEL is not "default" or None:
# misc.chroot_exec(('apt-get', 'install', '--yes', \
# config.KERNEL, '-q'))
#else: # use the kernel the user specified in the config.
if arch is not "amd64": # then use the 32bit 'linux-image-generic'
misc.chroot_exec(('apt-get', 'install', '--yes', \
'linux-image-generic', '-q'))
else: # use the amd64 'linux-signed-generic' for uEFI
misc.chroot_exec(('apt-get', 'install', '--yes', \
'linux-signed-generic', '-q'))

<br>
<br>
for starting the software just type into a console:<br>
sudo customizer-gui

There most of the things are pretty self-explainatory or described on the github page, we will be using the chroot console to setup our iso.
The following commands will setup the system:<br>
'''Basic Installation of programs<br>
echo "deb http://us.archive.ubuntu.com/ubuntu xenial main universe" >> /etc/apt/sources.list
echo "deb http://us.archive.ubuntu.com/ubuntu xenial main multiverse" >> /etc/apt/sources.list
dpkg --add-architecture i386
add-apt-repository ppa:freecad-maintainers/freecad-stable -y
add-apt-repository ppa:freecad-community/ppa -y
add-apt-repository ppa:thopiekar/cura -y
add-apt-repository ppa:maarten-baert/simplescreenrecorder -y
add-apt-repository ppa:js-reynaud/kicad-4 -y
add-apt-repository ppa:webupd8team/brackets -y
add-apt-repository ppa:freecad-maintainers/freecad-daily -y
add-apt-repository ppa:kdenlive/kdenlive-stable -y
add-apt-repository ppa:obsproject/obs-studio -y
apt-get update
apt-get upgrade -y
apt-get install freecad freecad-doc gimp inkscape audacity libavcodec-extra simplescreenrecorder librecad sweethome3d blender kicad openscad fritzing brackets gnumeric gnumeric-plugins-extra gnumeric-doc freecad-extras-drawing-dimensioning freecad-extras-assembly2 freecad-extras-fasteners gmic gimp-gmic git kdenlive vokoscreen chromium-browser freecad-daily debsums obs-studio -y

'''Installing Cura
apt-get install python-opengl python-serial -y
wget http://download.lulzbot.com/Software/Cura/Packages/Cura_21.08/debian/stretch/cura_21.08-f2748_amd64.deb (or the most current, check it)
dpkg -i cura_21.08-f2748_amd64.deb
rm cura_21.08-f2748_amd64.deb
printf "\nADD_EXTRA_GROUPS=1\nEXTRA_GROUPS="dialout"\n" >> /etc/adduser.conf

'''Install Arduino 1.6.8 (NOT the current)
wget https://downloads.arduino.cc/arduino-1.6.8-linux64.tar.xz
tar xvfJ arduino-1.6.8-linux64.tar.xz
rm arduino-1.6.8-linux64.tar.xz
mv arduino-1.6.8 /opt
'''and add the OSE Marlin to the examples
cd /opt/arduino-1.6.8/examples
mkdir OSE
download the file in http://opensourceecology.org/wiki/File:OSE_Marlin.zip
unzip OSE_Marlin.zip and put the contained file called Marlin in the OSE directory, then delete the rest
Give it the right to access it, with chown or simply: chmod 777 -R OSE (theres no inherent danger from that code when accessible)
additionally, make sure the last line of the cura setup is run, as this makes the actual communication with the boards possible.

'''installing inkscape export:
wget http://bigbluesaw.com/media/BigBlueSawDXFOutput-Version0.2.zip
unzip -o BigBlueSawDXFOutput-Version0.2.zip -d /usr/share/inkscape/extensions/
rm BigBlueSawDXFOutput-Version0.2.zip

'''installing threejs blender addon:
wget https://github.com/mrdoob/three.js/archive/master.zip
unzip master.zip
cp -r three.js-master/utils/exporters/blender/addons/io_three /usr/share/blender/scripts/addons
rm master.zip
rm -r three.js-master

'''jitsi extension:
nano /etc/chromium-browser/policies/managed/statkey.json
write in there
{
"ExtensionInstallForcelist":
["kglhbbefdnlheedjiejgomgmfplipfeb;https://clients2.google.com/service/update2/crx"]
}

'''Custom User settings<br>
Maybe delete some old stuff, like (this will be updated when the iso gets too bloated): <br>
sudo apt-get purge unity-webapps*
To make the user experience perfect, we need to adjust some user settings for the freshly logged in user. Unfortunately, the user for the live CD is created on the fly, therefore it cannot be preparated. However, it is possible to manipulate every new user that is created by providing their default folders and everything.<br>
This means, we will preparate the user by setting it up: Run the not created ISO by burning it to a stick, hosting it with a vm or similar, and set it up in a way that everything important is added and set. This includes cleaning the desktop and preparing the taskbar, starting Freecad and installing macros and commands there, and prepare Cura to create GCode for the OSE D3D Printer (More details on that is provided on the software list to the specific task). Additionally, the set setup.sh from the arduino folder must be run to make it a valid program for the user.<br>
When that is done, copy the ENTIRE personal folder (including all hidden folders) into a safe place in the network, as the live CD will not remember any changes. A Cloud, NAS, or simply [https://help.ubuntu.com/community/SSH/TransferFiles scp] will do the job, however remember not to leave traces, like a remembered password or personal data, as they will be replicated to every new User of the ISO!!!<br>
When you did that, copy all those files (the hidden included, better double check) into the (previously emptied) /etc/skel directory of your chroot (you can do that with scp as well as just adding it into the filesystem that is chrooted on the main system).<br>
The skel folder is basically replicated as a blueprint to every new created user, so every setting left there is then carried forward to the new created user. Rebuild the ISO, and you should be done!

==TODO==

This section will enumerate items for OSE Devs to work on for upcoming versions of OSE Linux.

===Requests and Notes===
*11/21/18 - mp4 and mkv don't play in default - need to install libraries
*11/16/18 - Firefox needs critical security updates
*11/16/18 - meet.jit.si/opensourceecology does not work in Chromium - can't access camera or mike. It does work in Firefox
*8/2/18 - please keep FreeCAD at v16 - not v17 or v18 - as v17 has a totally reworked, and more confusing workflow (more features, but less useful to the novice - and we don't intend to go beyong basic level of functionality for Design Jams, at least initially)
*8/2/18 - add [[Colmap]] photogrammetry to OSE Linux
*8/2/18 - update [[D3D_v18.07_Software]] with current D3D Marlin and .ini settings file for Lulzbot Cura.
*7/18 - Sweet Home 5.7 update - we have an older version
*7/18 - [[FlatCAM]] - used to generate toolpaths for D3D CNC Circuit Mill
*7/18 -[[QT]]- used to create Copper Carve
*7/18 -Copper Carve - [http://opencircuitinstitute.org/content/oci-copper-carve]. Used to control D3D CNC Circuit Mill. Ask Shane Oberloier
*7/18 -[[Processing Software]] addition (oscilloscope)
*6/18 -[[Piping Workbench]] addition to FreeCAD
*6/18 -[[FEA Workbench]] addition to FreeCAD
*6/21/18 - '''[[u8glib]] addition to Arduino Environment
*6/5/18 - Webm output of Kdenlive does not play without downloading extra packages. Make it play by downloading the appropriate software
** try installing vlc
*6/5/18 - Note that screen sharing in Jitsi Meet does not work in Chromium. Proper extensions need to be added.
*4/25/18 - Pronterface should be added to OSE Linux. This may help troubleshooting of printing.
*4/25/18 - Chromium allows only 3 or so tabs to be open before tabs no longer open, and a new Chromium window needs to be opened. (appears to be computer memory issue)
*4/23/18 - bug report. Downloaded http://opensourceecology.org/w/images/9/9b/OSE_Marlin.zip - and this could not be extracted on my desktop - "An error occurred while loading the archive". Extraction worked on another computer.
*4/23/18 - When trying to use Marlin from another USB - Could not open OSE Marlin (from another USB drive). Archive type not supported.
*Improve video - add which navigation style to use, and how to select a rotation plane. Next, use OSE Linux for the video, to remove any possibility of version difference. We should be able to teach someone Cube Readiness in 2 hours, and 3 more hours for video etc.
*2/1/18 - [[PVC Pipe and Fittings Library]] - verified that pipe, cross, elbow, alpha elbow, tee, and couplings now work in OSE Linux 1.0. These, combined with their 5 supporting CSV files, can now be added to OSE Linux.
*3/16/18 - SweetHome3D icon does not appear in applications menu, only in search box. Can we put it in the menu?

===Requirements===
*Follows Best Practices for creating a Linux distribution
*Download statistics are tracked - number vs. Time, and are displayed via a wiki script
*Single configuration with all of OSE-critical software
*Contains libraries - such as tractor design in FreeCAD, etc.
*Has a Team Charter for long term support
*Clear hosting strategy and admin
*Donation option with hosting transparency page of cost and uptime, and user statistics
*Download requires an email for future communications
*Clear OSE Social Contract - contract with the OSS/H community to keep this distribution open source for ever
*Clear contributor agreement
*Clear repositories for design - distributed and pulled into the OSE distribution as current working design libraries.

===Persistence===

We need to build in a simple way to persist data between reboots.

Marcin would like to be able to use OSE Linux full-time, but he would need to have his ssh key, keepass, etc all persisted between reboots. This, in general, is a necessary feature for anything more than "trying out" a distro. Because this data can be sensitive in nature (ie: ssh keys for logging into hetzner2), all persistent volumes should necessarily be encrypted.

The best experience I've had with Persistence in live distros was TAILS. There's no `dd` on the user side. They just go to "Applications -> System Tools -> Configure persistent volume", and set it up with the GUI.

TAILS is based on debian, as is OSE Linux, so I think this is a good place to start looking for how we can enable persistence in OSE Linux:

# https://tails.boum.org/contribute/design/persistence/#index3h2
# https://git-tails.immerda.ch/persistence-setup

For more info on this implementation, see [[OSE Linux Persistence]]

===Hashes & Signatures===

For every release of OSE Linux, there should be at least the following files in addition to the iso (arch specific) images:
# MD5SUMS
# MD5SUMS.gpg
# SHA1SUMS
# SHA1SUMS.gpg
# SHA256SUMS
# SHA256SUMS.gpg

This follows the standards as used by debian/ubuntu. For example, see the set of release files for ubuntu 18.04 here:

* https://mirrors.ocf.berkeley.edu/ubuntu-releases/18.04/

By following this procedure, we would provide a means for our users (after--say--spending many, many hours downloading the iso over a high-packet-loss sattelite internet connection) to validate that there was no corruption before they burn the image to a drive (a simple & fast step that can save days of debugging). Moreover, by releasing a cryptographic signature of these checksum files, we provide a means of authentication.

Note that, following best operational security practices, the cryptographic signature should be made from a subkey that is signed by an OSE primary key. The primary key should be in cold storage and only used on an air-gapped machine to sign subkeys. Those subkeys (which can be rotated) are the keys that are actually used to sign our releases' checksum files. For more information on this, see this [https://tails.boum.org/doc/about/openpgp_keys/index.en.html TAILS OpenPGP keys doc]

===OSE Linux Assists in Providing Technical Support===
Technical support is a service of huge importance to the OSE community. As a [[Distributive Enterprise]], OSE is interested in self-maintaining technical support base that can scale to millions of users.

To achieve this, part of our strategy is to utilize OSE Linux as an essential aspect of OSE's technical support. This is a managed distribution that works out all software-related issues for the OSE community - by providing a Linux distribution that just works.

Software-related issues stand in the way of seamless, distributed, open source collaboration. Overall, OSE Linux saves the OSE developer/user community thousands to millions of hours of total time that would otherwise be spent with people downloading software and making it work. To address this issue, OSE is proposing that any OSE user or developer obtains a copy of OSE Linux. This allows for a completely uniform way to eliminate all software related issues: improper installs, drivers, libraries, package conflicts, bad settings, security issues, software crashes, updates, and any other software issues. This is done by installing and using an entire OSE operating system, with all software prepared. The goal is to produce a stable and widely accessible system that can be run from a USB or that can be installed as a [[Multi-Boot System]]. The release schedule for updates will be quarterly.

=Version Change Log=
'''Oct 25 2017 - Version 1.0 release<br>
Added exploded part diagrams,vlc and obs<br>
Working arduino and cura (its now possible to write the code to the arduino/print with cura)<br>
Custom Wallpaper seems to work fine now.<br>
This version fixed all known issues (except the time zone, which is in the nature of Ubuntu). Therefore, this is version 1.0,
and this project will be seen as done until further changes are needed. <br>
The Download Link is [https://archive.org/download/OSELinux1.0/OSELinux1.0.iso here], [magnet:?xt=urn:btih:1b86fa4bdccea4308a115f7f0dbe9eeb93f37fe2&dn=OSELinux1.0&tr=http%3a%2f%2fbt1.archive.org%3a6969%2fannounce&tr=http%3a%2f%2fbt2.archive.org%3a6969%2fannounce&ws=http%3a%2f%2fia601504.us.archive.org%2f24%2fitems%2f&ws=http%3a%2f%2fia801504.us.archive.org%2f24%2fitems%2f&ws=https%3a%2f%2fia801504.us.archive.org%2f24%2fitems%2f magnet]

'''Sep 9 release<br>
All programs are now arranged to some extent, no setup of cura or freecad needed. All programs asked to date are added and functional. The screen is setup for the working with the OSE software and not just the default look.<br>
Some people came up with an issue regarding the ethernet connection, although there wasn't much testing yet, the top answer of this question may help [https://superuser.com/questions/351960/can-i-enable-wifi-on-a-ubuntu-live-cd Wifi Ubuntu Live CD]. This will be adressed when a solution is found.<br>
The Download Link is [https://drive.google.com/open?id=0ByUmXv7QXHeQQk9YYXNWYkdCcDQ here]

'''Sep 3 release<br>
same as last version, fixed some breaking bugs and added some basic options as default, as well as the program debsums. This version should be fully operable and its recommended updating to it<br>
The Download Link is [https://drive.google.com/file/d/0ByUmXv7QXHeQSU1vT01MYmJQb2s/view?usp=sharing here]

'''Aug 23 release <br>
A new version has been released with further, sophisticated options. Some of them are not in an optimal stage, so I am awaiting some feedback how the default should look like. That means setting up the different software parts in a way thats most convenient and sharing it in the [https://docs.google.com/spreadsheets/d/1hk1Tec4tkEDe47sEtRu7wySa8U4zYWBEat_dWZezQa0/edit#gid=0 software list]. As for now, in the /opt folder (filemanager > system > opt) there is the Macro sheet for freecad and the .ini for the d3d for Cura. The Marlin Software can be found in the examples os the arduino software<br>
The Download link is [https://drive.google.com/open?id=0ByUmXv7QXHeQUV9EVlozQUVNTFE here]

'''APR 28 hybrid release<br />
Link to shared Google Drive folder containing all versions[https://drive.google.com/drive/folders/0B3BMDf7eJE2IenozczVScXA0ZVk]<br />
OSE Live iso is named 4-28-17ose0.42.iso<br />'''
The Download Link is [https://drive.google.com/file/d/0B3BMDf7eJE2IOGR0enlFU0NBSGc/view?usp=sharing here]

'''February v0.3 release <br>
The Download Link is [https://drive.google.com/file/d/0B3BMDf7eJE2IM3F5V0ZLaHlBNUU/view?ts=58c8a40b here]<br>
Readme and Install Notes by Jai Kumar - [https://docs.google.com/document/d/1pwJHMRnuqmvdpJWd2PCmL_HzQrgnV4T3d4uwxFobtzM/edit Google Doc Link]

=OSE Linux Install Logs=
See [[OSE Linux Install Logs]]

=Links=
*[[OSE Linux Log]].
*'''[[OSE Linux Laptop List]]
* [[OSE Linux Persistence]]
*[[IT Support]]
*[[OSE Linux Testing - Marcin]]
*https://en.wikipedia.org/wiki/List_of_tools_to_create_Live_USB_systems
*'''[[OSE Linux v2.0]]'''

=Maintainers=
*[[Christian Rupp]] - v1 - 2017-present
*[[Jai Kumar]] - 2017 intial version
*[[Ray Log]] - v2 - 2019- present

=More=
{{Hint|Current issues - Mac Book Pro, Firefox, OSE Linux - video does not work - ''Failed to Access Camera''}}

{{Hint|Bug report: Lulzbot Cura has no heated bed turned on - change Machine settings so D3D has heated bed on out of the box.}}

{{Hint| OSE Linux is an Ubuntu 16.04 distribution with all of OSE's software, FreeCAD macros, Cura settings, and Marlin configured for the OSE 3D printer. Releases occur quarterly with updates. [[OSE_Linux#Requests_and_Notes]] shows required updates.}}
=USB Sticks=
*$1.84 Amazon - [https://www.amazon.com/50-4GB-Flash-Drive-Swivel/dp/B00H7IXA3C]
*$2.1 each 10 pack - [https://www.amazon.com/Swivel-Flash-Drive-Memory-Colors/dp/B00V5B2N3U/ref=asc_df_B00V5B2N3U/?tag=hyprod-20&linkCode=df0&hvadid=312760964359&hvpos=1o4&hvnetw=g&hvrand=6511301743991622793&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9023315&hvtargid=pla-608086117341&psc=1]
*$2.1 100 pack - [https://www.amazon.com/Aretop-Premium-Pendrive-Package-Storage/dp/B07S3TR6F7/ref=sr_1_3?keywords=100+pack+usb+stick+4gb&qid=1575667494&s=electronics&sr=1-3]
*1000 at $2.41

=Log=
*[[OSE Linux Log]]

OSE Linux - 2.0 version from 2020

2021-02-14T21:13:34Z

Pizzooid: /* How To Create an OSE Linux USB using Windows */

{{Hint|'''OSE Linux 2.0 is coming out at the end of August - try a preview - https://www.caldorkids.com/ose/}}

{{Hint|You are welcome to download OSE Linux and make a live USB. We can also send you a USB stick withe the live OSE Linux distribution. To receive a copy by mail, please send $10 through our <html>
<form action="https://www.paypal.com/cgi-bin/webscr" method="post" target="_top">
<input type="hidden" name="cmd" value="_s-xclick" />
<input type="hidden" name="hosted_button_id" value="5XFQZM7X9B3JE" />
<input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif" border="0" name="submit" title="PayPal - The safer, easier way to pay online!" alt="Donate with PayPal button" />
<img alt="" border="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif" width="1" height="1" />
</form>

</html> button, and include your address when you go through PayPal. You can also send us a check. See [[Donate]] page for more options, or email info at opensourceecology dot org.}}

=What is It?=

[[Image:oselinux.jpg|thumb|OSE software stack.]]

'''OSE Linux''' is a freely downloadable operating system that contains all software that is used regularly at OSE. It is run as a [[Live USB]] without the user having to modify or upset their usual operating system in any way whatsoever. This provides access to exactly the same software that we use during workshops and other training sessions - to avoid differences in versions common to different operating systems. During our training sessions, we will use OSE Linux ourselves - so your programs will look exactly like ours. This addresses hours of potentially wasted time due to differences in software or software not working.

OSE Linux also addresses the tens of hours that it would potentially take to download and configure all the software and libraries in common use by OSE. Instead, a single install, taking under half hour of dedicated user time after download, is sufficient to download the entire operating system. This is useful in large-scale collaborative processes - where everyone should use the exact same system to promote a seamless experience.

It is a good practice for [[OSE Developers]] to download and use the system to avoid software malfunction, improper settings, and in general the time it takes to download or install various software and its extensions, such as additional workbenches in FreeCAD, browser plugins, etc. OSE uses only open source software to produce all of its work product to facilitate interoperability with a large global team of developers.

'''Please note that OSE uses a lot of custom software - so please save yourself hours of install time and and just download the prepared OSE Linux. We are doing this to make your life easy. Note also that you should not run OSE Linux in a Virtual Machine, as a Virtual Machine will be much slower at computation intensive tasks such as CAD.'''

OSE Linux can be used by downloading the ISO, and creating a bootable USB stick. Instead of using one's regular operating system, one can choose - upon startup - to run the OSE Linux operating system from a USB stick, without installing it on one's hard drive. '''Note that currently you can't save files on the Live Linux - so upload any documents to your log, the wiki, or use cloud-documents where data is not saved locally.'''

==OSE Linux at Workshops==
For reasons of software uniformity, we like to use OSE Linux. Our experience with prior workshops at OSE which involve software training was that always there was someone who could not run some software properly, or there would be some differences in the software on different platforms. This typically obstructed smooth progress of everyone following along during software training. For this reason, we like to use OSE Linux live, so that everyone has the exact same copy. All that people need to do is to boot from our USB. Once booted, uniform results are pretty much guaranteed. Thus, we begun using OSE Linux in 2017 as a regular practice during OSE workshops - where participants are instructed to either make their own USB at home - or we provide the USB at the OSE site.

=OSE Linux v2.0=

'''Download the 7.2G file at: https://www.caldorkids.com/ose/

See [[OSE Linux v2 Notes]]
==Software List==
This is a list of software on OSE Linux 2. The selection of software is evolving for the needs of regenerative solutions at scale.

<html><iframe src="https://docs.google.com/spreadsheets/d/1hk1Tec4tkEDe47sEtRu7wySa8U4zYWBEat_dWZezQa0/pubhtml?widget=true&headers=false" height=500 width=800></iframe></html>

[https://docs.google.com/spreadsheets/d/1hk1Tec4tkEDe47sEtRu7wySa8U4zYWBEat_dWZezQa0/ edit]

==Software Notes==
*[[OSE Linux 2 Software Notes]]
*Mixxx - digital DJ platform to [[Twitch]]

=Download and Install OSE Linux Live ISO=
Requirements: ISO image, 4 GB USB stick
==v1.0 from 2017==

Download the [https://en.wikipedia.org/wiki/ISO_image .ISO Image] file below. This will then be installed onto a USB flash drive to create a [https://en.wikipedia.org/wiki/Live_USB Live USB].

* [https://archive.org/details/OSELinux1.0 Internet Archive]
* [https://archive.org/details/OSELinux1.0 Torrent]
* [magnet:?xt=urn:btih:1b86fa4bdccea4308a115f7f0dbe9eeb93f37fe2&dn=OSELinux1.0&tr=http%3a%2f%2fbt1.archive.org%3a6969%2fannounce&tr=http%3a%2f%2fbt2.archive.org%3a6969%2fannounce&ws=http%3a%2f%2fia601504.us.archive.org%2f24%2fitems%2f&ws=http%3a%2f%2fia801504.us.archive.org%2f24%2fitems%2f&ws=https%3a%2f%2fia801504.us.archive.org%2f24%2fitems%2f Magnet Link]

==How To Create an OSE Linux USB using Ubunutu==

Objective: A bootable USB stick that provides the OSE Live desktop, and will run all the OSE programs without touching any existing locally installed OS on the computer.
It's a way to test, and use, the OSE programs (3D design, 2D design, video capture and edit, resource management) and not disturb the current computer setup.

1. Download the ISO (See above for current ISO URL) <br />
2. Burn ISO to USB<br />
For Setting up the USB stick, follow the instructions [[How_to:Write_Image_to_SD_Card]], <br>
simply swap the word SD for USB. There are no customizations to be made as they are suggested at the bottom, all is working out of the box.

3. Boot your computer with the USB. See [[OSE Linux#Getting Started]]

<br><br><br><br>
'''Here is the video HowTo for Ubuntu 16.04 users, GUI version'''<br>
<html><video height="400" controls>
<source src="https://wiki.opensourceecology.org/images/2/23/OSE_Live_USB_HowTo.webm" type="video/webm">
Your browser does not support the video tag.
</video></html>

http://opensourceecology.org/w/images/2/23/OSE_Live_USB_HowTo.webm

<html><iframe src="https://docs.google.com/document/d/1w2kDCAVJSsMwQuX4gstq-YLM0X2l32H6cTlbD2zwJM4/pub?embedded=true" height=400 width=80%></iframe></html>

[https://docs.google.com/document/d/1w2kDCAVJSsMwQuX4gstq-YLM0X2l32H6cTlbD2zwJM4/ edit]

==How To Create an OSE Linux USB using Windows==

[https://rufus.akeo.ie/#download Download Rufus]

<html><iframe src="https://docs.google.com/document/d/1baJdLIh1m7_VjUoDq2-9P1LWRzwUcQkxhl0ZNB_6WoU/pub?embedded=true" height=400 width=80%></iframe></html>

[https://docs.google.com/document/d/1baJdLIh1m7_VjUoDq2-9P1LWRzwUcQkxhl0ZNB_6WoU/ edit]

===Setting up the OSE_OS on a Virtual Machine (using VirtualBox) on a Windows System.===
The links below would help with: '''Setting up the OSE_OS on a Virtual Machine (using VirtualBox) on a Windows System.'''<br>
Note that some lag might be experienced with such an installation depending on your system specs and some OpenGL glitches have been reported in the past though they seem currently resolved. If the ability to switch seamlessly from Ubuntu to Windows without having to reboot is essential as an option, it might be worth a try:<br>
[http://www.psychocats.net/ubuntu/virtualbox Installing Ubuntu inside Windows using VirtualBox]<br>
[https://www.howtogeek.com/howto/2845/install-guest-additions-to-windows-and-linux-vms-in-virtualbox/ Install Guest Additions to Windows and Linux VMs in VirtualBox]<br>
[https://www.howtogeek.com/187703/how-to-access-folders-on-your-host-machine-from-an-ubuntu-virtual-machine-in-virtualbox/ How to Access Folders on Your Host Machine from an Ubuntu Virtual Machine in VirtualBox]

==How To Create an OSE Linux USB using Mac==
Key Howtos:
*From Tom - [https://tutorials.ubuntu.com/tutorial/tutorial-create-a-usb-stick-on-macos#0]
*'''[https://gist.github.com/gregoryfoster/35d8037a6a8424661a8a2606c1280785 How To Create a bootable Open Source Ecology (OSE) Linux USB Stick on Mac OS X - github]'''
*[[How to Create an OSE Linux USB using Mac Guide by Alex Au 2018]]

'''Download'''

Download the latest OSE Linux ISO disk image [[OSE_Linux#Download_and_Install_OSE_Linux_Live_ISO]].

'''Insert your USB Stick and determine its device identifier'''

# Insert USB stick
# Open a Terminal window
# Determine USB stick device ID: `diskutil list`

<nowiki>

$ diskutil list
...
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: *16.0 GB disk3
</nowiki>

'''Create a bootable USB Stick from a hybrid disk image'''

Using a hybrid ISO disk image is by far the simpler approach as you just overwrite the entire USB stick.

# Unmount all partitions on device: `diskutil unmountDisk [Device ID]`
# Copy ISO: `sudo dd if=[Path to ISO] of=[Device ID] bs=1048576`
#* Press CTRL+T to send a SIGINFO signal to `dd` to track progress [http://osxdaily.com/2015/06/05/copy-iso-to-usb-drive-mac-os-x-command/#comment-1718523 source]

<nowiki>

$ diskutil unmountDisk /dev/disk3
Unmount of all volumes on disk3 was successful
$ sudo dd if=~/Downloads/ose0.3isohybrid.iso of=/dev/disk3 bs=1048576
2142+0 records in
2142+0 records out
2246049792 bytes transferred in 1841.710284 secs (1219546 bytes/sec)
</nowiki>

The partition is automatically marked as as bootable.

Eject USB Stick: `diskutil eject [Device ID]`

<nowiki>

$ diskutil eject /dev/disk3
Disk /dev/disk3 ejected
</nowiki>

And you're good to go.

=Getting Started=
'''Instructions for using OSE Linux for the first time'''

==Booting Up and BIOS Settings==

After powering on your computer, but before your normal operating system starts, you can access your boot settings.

'''Boot target computer from USB Stick'''

First, configure the BIOS to prioritize booting from a USB drive. In my case, I'm installing on an HP Spectre x360 laptop [http://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery/How-to-boot-from-USB-flash-drive-HP-Spectre-x360/td-p/5032935].

# Power up HP Spectre x360
# Press `F10` to enter the BIOS
# Navigate to System Configuration
# Select Boot Options
## Disable Secure Boot
## Enable Legacy Boot
## In UEFI Boot Order move USB Diskette to top of list
## In Legacy Boot Order move USB Diskette to top of list
## Disable 3D Graphic Acceleration
# Press `F10` to save changes and exit BIOS

Your system will restart, recognize the USB Stick, and boot its contents.

_For existing Linux systems with a boot manager installed, you may still need to intervene to select an alternative boot option. Press `F9` to enter Boot Options and choose the USB Disk._

==Software Tutorials==

*[[FreeCAD 101]]
**[[Old FreeCAD Tests]]
*[https://en.wikibooks.org/wiki/OpenSCAD_User_Manual OpenSCAD wikibook]

=Testing=

We are documenting which systems work successfully for Live boot and/or install of the OSE Linux ISO.

Please document 3 things:
#Version of the OSE Linux you are trying to boot and/or install - date or link to the download from above. Note that new versions will be published quarterly. It is impotant to keep notes on the specific version that you are using so there is no confusion on which OSE Linux versions are successful
#Hardware you are using, such as Dell Precision M6500 Laptop
#Operating system that you are using on your hardware - such as Ubuntu 16.04.

To document this for your system, please go to See [[ISO to USB Install Notes]]. The test should verify the following specific usage points, and receive "100% tested and working" condition for the ISO to be considered done (ie, for example, we cannot have the Dimension Drawing Workbench not working in FreeCAD. For the specific usage points that are marked "Not Cricital", they do not count in the grading.

#Is the time zone set correctly? (Not critical)
#[[File:check.png]] Does Chromium connect to wireless internet without a problem?
#Is the version of Arduino 1.6.8 as the default?
#Does Arduino IDE upload sample program to the Mega after selecting the correct board and port under Tools?
#Is OSE Marlin available within Arduino?
#Can you download a file from Part Library on the wiki and open it in FreeCAD?
#Does the Exploded Part Animation workbench create part explosions without crashing?
#Do files download to the desktop (so a new user can find files immediately without having to find the Downloads folder in the directory structure)?
#Can you upload files to the wiki, such as an image?

=Troubleshooting=
*[[How to Troubleshoot Wireless on OSE Linux]]

=OSE Linux Development=
'''This section is used by developers making OSE Linux'''

==How To Create the ISO File Using Ubuntu==
We are using the customizer by kamilion:
<br>
https://github.com/kamilion/customizer/wiki/First-guide
<br>
however, there is a problem with the iso creation process:
we need to modify the source code, as the kernel download will otherwise fail and disturb the creation of the iso. This has of course to be done before the compiling into a deb file. For that, we have to edit:<br>
/{Unzipped Master}/src/actions/rebuild.py
go to the line <br>
detect_boot()
and look under it, there should be a line going like <br>
if config.KERNEL is not default
comment that out (with #) until next else (including the else) and then correct the intendation (as python is very sensitive to that), meaning everything to the next empty line has to be moved left one 4 whitespaces. In the end, it should look like this:
#if config.KERNEL is not "default" or None:
# misc.chroot_exec(('apt-get', 'install', '--yes', \
# config.KERNEL, '-q'))
#else: # use the kernel the user specified in the config.
if arch is not "amd64": # then use the 32bit 'linux-image-generic'
misc.chroot_exec(('apt-get', 'install', '--yes', \
'linux-image-generic', '-q'))
else: # use the amd64 'linux-signed-generic' for uEFI
misc.chroot_exec(('apt-get', 'install', '--yes', \
'linux-signed-generic', '-q'))

<br>
<br>
for starting the software just type into a console:<br>
sudo customizer-gui

There most of the things are pretty self-explainatory or described on the github page, we will be using the chroot console to setup our iso.
The following commands will setup the system:<br>
'''Basic Installation of programs<br>
echo "deb http://us.archive.ubuntu.com/ubuntu xenial main universe" >> /etc/apt/sources.list
echo "deb http://us.archive.ubuntu.com/ubuntu xenial main multiverse" >> /etc/apt/sources.list
dpkg --add-architecture i386
add-apt-repository ppa:freecad-maintainers/freecad-stable -y
add-apt-repository ppa:freecad-community/ppa -y
add-apt-repository ppa:thopiekar/cura -y
add-apt-repository ppa:maarten-baert/simplescreenrecorder -y
add-apt-repository ppa:js-reynaud/kicad-4 -y
add-apt-repository ppa:webupd8team/brackets -y
add-apt-repository ppa:freecad-maintainers/freecad-daily -y
add-apt-repository ppa:kdenlive/kdenlive-stable -y
add-apt-repository ppa:obsproject/obs-studio -y
apt-get update
apt-get upgrade -y
apt-get install freecad freecad-doc gimp inkscape audacity libavcodec-extra simplescreenrecorder librecad sweethome3d blender kicad openscad fritzing brackets gnumeric gnumeric-plugins-extra gnumeric-doc freecad-extras-drawing-dimensioning freecad-extras-assembly2 freecad-extras-fasteners gmic gimp-gmic git kdenlive vokoscreen chromium-browser freecad-daily debsums obs-studio -y

'''Installing Cura
apt-get install python-opengl python-serial -y
wget http://download.lulzbot.com/Software/Cura/Packages/Cura_21.08/debian/stretch/cura_21.08-f2748_amd64.deb (or the most current, check it)
dpkg -i cura_21.08-f2748_amd64.deb
rm cura_21.08-f2748_amd64.deb
printf "\nADD_EXTRA_GROUPS=1\nEXTRA_GROUPS="dialout"\n" >> /etc/adduser.conf

'''Install Arduino 1.6.8 (NOT the current)
wget https://downloads.arduino.cc/arduino-1.6.8-linux64.tar.xz
tar xvfJ arduino-1.6.8-linux64.tar.xz
rm arduino-1.6.8-linux64.tar.xz
mv arduino-1.6.8 /opt
'''and add the OSE Marlin to the examples
cd /opt/arduino-1.6.8/examples
mkdir OSE
download the file in http://opensourceecology.org/wiki/File:OSE_Marlin.zip
unzip OSE_Marlin.zip and put the contained file called Marlin in the OSE directory, then delete the rest
Give it the right to access it, with chown or simply: chmod 777 -R OSE (theres no inherent danger from that code when accessible)
additionally, make sure the last line of the cura setup is run, as this makes the actual communication with the boards possible.

'''installing inkscape export:
wget http://bigbluesaw.com/media/BigBlueSawDXFOutput-Version0.2.zip
unzip -o BigBlueSawDXFOutput-Version0.2.zip -d /usr/share/inkscape/extensions/
rm BigBlueSawDXFOutput-Version0.2.zip

'''installing threejs blender addon:
wget https://github.com/mrdoob/three.js/archive/master.zip
unzip master.zip
cp -r three.js-master/utils/exporters/blender/addons/io_three /usr/share/blender/scripts/addons
rm master.zip
rm -r three.js-master

'''jitsi extension:
nano /etc/chromium-browser/policies/managed/statkey.json
write in there
{
"ExtensionInstallForcelist":
["kglhbbefdnlheedjiejgomgmfplipfeb;https://clients2.google.com/service/update2/crx"]
}

'''Custom User settings<br>
Maybe delete some old stuff, like (this will be updated when the iso gets too bloated): <br>
sudo apt-get purge unity-webapps*
To make the user experience perfect, we need to adjust some user settings for the freshly logged in user. Unfortunately, the user for the live CD is created on the fly, therefore it cannot be preparated. However, it is possible to manipulate every new user that is created by providing their default folders and everything.<br>
This means, we will preparate the user by setting it up: Run the not created ISO by burning it to a stick, hosting it with a vm or similar, and set it up in a way that everything important is added and set. This includes cleaning the desktop and preparing the taskbar, starting Freecad and installing macros and commands there, and prepare Cura to create GCode for the OSE D3D Printer (More details on that is provided on the software list to the specific task). Additionally, the set setup.sh from the arduino folder must be run to make it a valid program for the user.<br>
When that is done, copy the ENTIRE personal folder (including all hidden folders) into a safe place in the network, as the live CD will not remember any changes. A Cloud, NAS, or simply [https://help.ubuntu.com/community/SSH/TransferFiles scp] will do the job, however remember not to leave traces, like a remembered password or personal data, as they will be replicated to every new User of the ISO!!!<br>
When you did that, copy all those files (the hidden included, better double check) into the (previously emptied) /etc/skel directory of your chroot (you can do that with scp as well as just adding it into the filesystem that is chrooted on the main system).<br>
The skel folder is basically replicated as a blueprint to every new created user, so every setting left there is then carried forward to the new created user. Rebuild the ISO, and you should be done!

==TODO==

This section will enumerate items for OSE Devs to work on for upcoming versions of OSE Linux.

===Requests and Notes===
*11/21/18 - mp4 and mkv don't play in default - need to install libraries
*11/16/18 - Firefox needs critical security updates
*11/16/18 - meet.jit.si/opensourceecology does not work in Chromium - can't access camera or mike. It does work in Firefox
*8/2/18 - please keep FreeCAD at v16 - not v17 or v18 - as v17 has a totally reworked, and more confusing workflow (more features, but less useful to the novice - and we don't intend to go beyong basic level of functionality for Design Jams, at least initially)
*8/2/18 - add [[Colmap]] photogrammetry to OSE Linux
*8/2/18 - update [[D3D_v18.07_Software]] with current D3D Marlin and .ini settings file for Lulzbot Cura.
*7/18 - Sweet Home 5.7 update - we have an older version
*7/18 - [[FlatCAM]] - used to generate toolpaths for D3D CNC Circuit Mill
*7/18 -[[QT]]- used to create Copper Carve
*7/18 -Copper Carve - [http://opencircuitinstitute.org/content/oci-copper-carve]. Used to control D3D CNC Circuit Mill. Ask Shane Oberloier
*7/18 -[[Processing Software]] addition (oscilloscope)
*6/18 -[[Piping Workbench]] addition to FreeCAD
*6/18 -[[FEA Workbench]] addition to FreeCAD
*6/21/18 - '''[[u8glib]] addition to Arduino Environment
*6/5/18 - Webm output of Kdenlive does not play without downloading extra packages. Make it play by downloading the appropriate software
** try installing vlc
*6/5/18 - Note that screen sharing in Jitsi Meet does not work in Chromium. Proper extensions need to be added.
*4/25/18 - Pronterface should be added to OSE Linux. This may help troubleshooting of printing.
*4/25/18 - Chromium allows only 3 or so tabs to be open before tabs no longer open, and a new Chromium window needs to be opened. (appears to be computer memory issue)
*4/23/18 - bug report. Downloaded http://opensourceecology.org/w/images/9/9b/OSE_Marlin.zip - and this could not be extracted on my desktop - "An error occurred while loading the archive". Extraction worked on another computer.
*4/23/18 - When trying to use Marlin from another USB - Could not open OSE Marlin (from another USB drive). Archive type not supported.
*Improve video - add which navigation style to use, and how to select a rotation plane. Next, use OSE Linux for the video, to remove any possibility of version difference. We should be able to teach someone Cube Readiness in 2 hours, and 3 more hours for video etc.
*2/1/18 - [[PVC Pipe and Fittings Library]] - verified that pipe, cross, elbow, alpha elbow, tee, and couplings now work in OSE Linux 1.0. These, combined with their 5 supporting CSV files, can now be added to OSE Linux.
*3/16/18 - SweetHome3D icon does not appear in applications menu, only in search box. Can we put it in the menu?

===Requirements===
*Follows Best Practices for creating a Linux distribution
*Download statistics are tracked - number vs. Time, and are displayed via a wiki script
*Single configuration with all of OSE-critical software
*Contains libraries - such as tractor design in FreeCAD, etc.
*Has a Team Charter for long term support
*Clear hosting strategy and admin
*Donation option with hosting transparency page of cost and uptime, and user statistics
*Download requires an email for future communications
*Clear OSE Social Contract - contract with the OSS/H community to keep this distribution open source for ever
*Clear contributor agreement
*Clear repositories for design - distributed and pulled into the OSE distribution as current working design libraries.

===Persistence===

We need to build in a simple way to persist data between reboots.

Marcin would like to be able to use OSE Linux full-time, but he would need to have his ssh key, keepass, etc all persisted between reboots. This, in general, is a necessary feature for anything more than "trying out" a distro. Because this data can be sensitive in nature (ie: ssh keys for logging into hetzner2), all persistent volumes should necessarily be encrypted.

The best experience I've had with Persistence in live distros was TAILS. There's no `dd` on the user side. They just go to "Applications -> System Tools -> Configure persistent volume", and set it up with the GUI.

TAILS is based on debian, as is OSE Linux, so I think this is a good place to start looking for how we can enable persistence in OSE Linux:

# https://tails.boum.org/contribute/design/persistence/#index3h2
# https://git-tails.immerda.ch/persistence-setup

For more info on this implementation, see [[OSE Linux Persistence]]

===Hashes & Signatures===

For every release of OSE Linux, there should be at least the following files in addition to the iso (arch specific) images:
# MD5SUMS
# MD5SUMS.gpg
# SHA1SUMS
# SHA1SUMS.gpg
# SHA256SUMS
# SHA256SUMS.gpg

This follows the standards as used by debian/ubuntu. For example, see the set of release files for ubuntu 18.04 here:

* https://mirrors.ocf.berkeley.edu/ubuntu-releases/18.04/

By following this procedure, we would provide a means for our users (after--say--spending many, many hours downloading the iso over a high-packet-loss sattelite internet connection) to validate that there was no corruption before they burn the image to a drive (a simple & fast step that can save days of debugging). Moreover, by releasing a cryptographic signature of these checksum files, we provide a means of authentication.

Note that, following best operational security practices, the cryptographic signature should be made from a subkey that is signed by an OSE primary key. The primary key should be in cold storage and only used on an air-gapped machine to sign subkeys. Those subkeys (which can be rotated) are the keys that are actually used to sign our releases' checksum files. For more information on this, see this [https://tails.boum.org/doc/about/openpgp_keys/index.en.html TAILS OpenPGP keys doc]

===OSE Linux Assists in Providing Technical Support===
Technical support is a service of huge importance to the OSE community. As a [[Distributive Enterprise]], OSE is interested in self-maintaining technical support base that can scale to millions of users.

To achieve this, part of our strategy is to utilize OSE Linux as an essential aspect of OSE's technical support. This is a managed distribution that works out all software-related issues for the OSE community - by providing a Linux distribution that just works.

Software-related issues stand in the way of seamless, distributed, open source collaboration. Overall, OSE Linux saves the OSE developer/user community thousands to millions of hours of total time that would otherwise be spent with people downloading software and making it work. To address this issue, OSE is proposing that any OSE user or developer obtains a copy of OSE Linux. This allows for a completely uniform way to eliminate all software related issues: improper installs, drivers, libraries, package conflicts, bad settings, security issues, software crashes, updates, and any other software issues. This is done by installing and using an entire OSE operating system, with all software prepared. The goal is to produce a stable and widely accessible system that can be run from a USB or that can be installed as a [[Multi-Boot System]]. The release schedule for updates will be quarterly.

=Version Change Log=
'''Oct 25 2017 - Version 1.0 release<br>
Added exploded part diagrams,vlc and obs<br>
Working arduino and cura (its now possible to write the code to the arduino/print with cura)<br>
Custom Wallpaper seems to work fine now.<br>
This version fixed all known issues (except the time zone, which is in the nature of Ubuntu). Therefore, this is version 1.0,
and this project will be seen as done until further changes are needed. <br>
The Download Link is [https://archive.org/download/OSELinux1.0/OSELinux1.0.iso here], [magnet:?xt=urn:btih:1b86fa4bdccea4308a115f7f0dbe9eeb93f37fe2&dn=OSELinux1.0&tr=http%3a%2f%2fbt1.archive.org%3a6969%2fannounce&tr=http%3a%2f%2fbt2.archive.org%3a6969%2fannounce&ws=http%3a%2f%2fia601504.us.archive.org%2f24%2fitems%2f&ws=http%3a%2f%2fia801504.us.archive.org%2f24%2fitems%2f&ws=https%3a%2f%2fia801504.us.archive.org%2f24%2fitems%2f magnet]

'''Sep 9 release<br>
All programs are now arranged to some extent, no setup of cura or freecad needed. All programs asked to date are added and functional. The screen is setup for the working with the OSE software and not just the default look.<br>
Some people came up with an issue regarding the ethernet connection, although there wasn't much testing yet, the top answer of this question may help [https://superuser.com/questions/351960/can-i-enable-wifi-on-a-ubuntu-live-cd Wifi Ubuntu Live CD]. This will be adressed when a solution is found.<br>
The Download Link is [https://drive.google.com/open?id=0ByUmXv7QXHeQQk9YYXNWYkdCcDQ here]

'''Sep 3 release<br>
same as last version, fixed some breaking bugs and added some basic options as default, as well as the program debsums. This version should be fully operable and its recommended updating to it<br>
The Download Link is [https://drive.google.com/file/d/0ByUmXv7QXHeQSU1vT01MYmJQb2s/view?usp=sharing here]

'''Aug 23 release <br>
A new version has been released with further, sophisticated options. Some of them are not in an optimal stage, so I am awaiting some feedback how the default should look like. That means setting up the different software parts in a way thats most convenient and sharing it in the [https://docs.google.com/spreadsheets/d/1hk1Tec4tkEDe47sEtRu7wySa8U4zYWBEat_dWZezQa0/edit#gid=0 software list]. As for now, in the /opt folder (filemanager > system > opt) there is the Macro sheet for freecad and the .ini for the d3d for Cura. The Marlin Software can be found in the examples os the arduino software<br>
The Download link is [https://drive.google.com/open?id=0ByUmXv7QXHeQUV9EVlozQUVNTFE here]

'''APR 28 hybrid release<br />
Link to shared Google Drive folder containing all versions[https://drive.google.com/drive/folders/0B3BMDf7eJE2IenozczVScXA0ZVk]<br />
OSE Live iso is named 4-28-17ose0.42.iso<br />'''
The Download Link is [https://drive.google.com/file/d/0B3BMDf7eJE2IOGR0enlFU0NBSGc/view?usp=sharing here]

'''February v0.3 release <br>
The Download Link is [https://drive.google.com/file/d/0B3BMDf7eJE2IM3F5V0ZLaHlBNUU/view?ts=58c8a40b here]<br>
Readme and Install Notes by Jai Kumar - [https://docs.google.com/document/d/1pwJHMRnuqmvdpJWd2PCmL_HzQrgnV4T3d4uwxFobtzM/edit Google Doc Link]

=OSE Linux Install Logs=
See [[OSE Linux Install Logs]]

=Links=
*[[OSE Linux Log]].
*'''[[OSE Linux Laptop List]]
* [[OSE Linux Persistence]]
*[[IT Support]]
*[[OSE Linux Testing - Marcin]]
*https://en.wikipedia.org/wiki/List_of_tools_to_create_Live_USB_systems
*'''[[OSE Linux v2.0]]'''

=Maintainers=
*[[Christian Rupp]] - v1 - 2017-present
*[[Jai Kumar]] - 2017 intial version
*[[Ray Log]] - v2 - 2019- present

=More=
{{Hint|Current issues - Mac Book Pro, Firefox, OSE Linux - video does not work - ''Failed to Access Camera''}}

{{Hint|Bug report: Lulzbot Cura has no heated bed turned on - change Machine settings so D3D has heated bed on out of the box.}}

{{Hint| OSE Linux is an Ubuntu 16.04 distribution with all of OSE's software, FreeCAD macros, Cura settings, and Marlin configured for the OSE 3D printer. Releases occur quarterly with updates. [[OSE_Linux#Requests_and_Notes]] shows required updates.}}
=USB Sticks=
*$1.84 Amazon - [https://www.amazon.com/50-4GB-Flash-Drive-Swivel/dp/B00H7IXA3C]
*$2.1 each 10 pack - [https://www.amazon.com/Swivel-Flash-Drive-Memory-Colors/dp/B00V5B2N3U/ref=asc_df_B00V5B2N3U/?tag=hyprod-20&linkCode=df0&hvadid=312760964359&hvpos=1o4&hvnetw=g&hvrand=6511301743991622793&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9023315&hvtargid=pla-608086117341&psc=1]
*$2.1 100 pack - [https://www.amazon.com/Aretop-Premium-Pendrive-Package-Storage/dp/B07S3TR6F7/ref=sr_1_3?keywords=100+pack+usb+stick+4gb&qid=1575667494&s=electronics&sr=1-3]
*1000 at $2.41

=Log=
*[[OSE Linux Log]]

Talk:OSE Linux Docker

2021-02-13T21:53:09Z

Pizzooid:

I tried to install OSE Linux on a USB-stick but I did not succeed with the persistent feature. What is your current setup?
Have you thought about using docker to get exactly the same program versions instead of your own distribution?
Docker files would be much easier to maintain and use without changing the operating system.
e.g.: [https://blog.jessfraz.com/post/docker-containers-on-the-desktop/]

Pizzooid Log

2021-02-13T21:51:46Z

Pizzooid:

== Sat Feb 13, 2021==
[[Talk:OSE Linux Docker]], [[Talk:The Case for Using Wiki Version History#Continued Argumentation]]

== Wed Feb 10, 2021 ==
Setup [[OSE Linux]] USB Drive.

== Sat Feb 6, 2021 ==
[[Talk:The Case for Using Wiki Version History]]

User:Pizzooid

2021-02-13T21:48:31Z

Pizzooid:

I've finished my Ph.D. in physics in 2018.
After that, I have been working at the Austrian Institute of Technology for a little over a year.
Right now I am traveling with my wife and I figured that I could contribute to this project while traveling by cleaning the wiki up a little bit here and there. pietro at palmesi

http://palmesi.com/

[[Pizzooid Log]]

Pietro Log

2021-02-13T21:48:04Z

Pizzooid: Pizzooid moved page Pietro Log to Pizzooid Log: So that the Username and Log name are the same

#REDIRECT [[Pizzooid Log]]

Pizzooid Log

2021-02-13T21:48:04Z

Pizzooid: Pizzooid moved page Pietro Log to Pizzooid Log: So that the Username and Log name are the same

== Wed Feb 10, 2021 ==
Setup [[OSE Linux]] USB Drive.

== Sat Feb 6, 2021 ==
[[Talk:The Case for Using Wiki Version History]]

User:Pizzooid

2021-02-13T21:47:12Z

Pizzooid:

Talk:OSE Linux Docker

2021-02-13T21:46:26Z

Pizzooid: Created page with "I tried to install OSE Linux on a USB-stick but I did not succeed with the persistent feature.What is your current setup? Have you thought about using docker to get exactly t..."

I tried to install OSE Linux on a USB-stick but I did not succeed with the persistent feature.What is your current setup?
Have you thought about using docker to get exactly the same program versions instead of your own distribution?
Docker files would be much easier to maintain and use without changing the operating system.

Talk:The Case for Using Wiki Version History

2021-02-13T21:33:19Z

Pizzooid:

=Meta-Discussion=
Major advantages on git - what are those advantages? What problem are we trying to solve?

Once we are clear on advantages, and problem we are solving - we have an answer.

The first question for you - what are those advantages of Git that our workflow can benefit from? What problem is a Git platform solving that is important to us, that is not addressed by the wiki versioning?

==Major Advantages==
#'''Support''' MediaWiki’s major target is Wikipedia. Wikipedia was not intended to be used as a development environment but rather as an encyclopedia. Support and for using it as a version control system is likely going to be limited.
#'''Robustness''' - Git is well tested as a versioning system vs not many people use MediaWiki as a versioning tool.
#'''Data Replication''' - With git every collaborator has a copy of the file, they could work even when the server is down. Should a problem with the server happen, every collaborator has a backup.
#'''Versions have a hash key''' - In Git every commit has a unique hash key it can be referred to. A version can always be linked to by its unique hash - In Wikipedia on the other hand there is only a timestamp and the current version <strike>changes</strike> retains its link after a new version is added. Old versions can be accessed directly via their unique link.
#'''Extensibility/Automation''' - Git servers usually have the ability to do certain tasks when a new version is uploaded. A continuous integration server can automatically check files for correctness and create preview images.
#'''Access Control''' - In git, a part of the developers can be maintainers that first have to check changes before they make it into the official version.
#'''Accidental Overwrites'''- In Wikipedia two people could submit a file at the same moment and not see that another person did the same, one of the commits would be overwritten - Git prohibits this behavior. That said, I can see that WikiMedia might just be good enough for now but I would also be open to doing a few demos on how git could be used as an alternative.

'''Is any one of the reasons important enough?'''

==Counterarguments on Major Advantages==

#'''Support''' - Wikipedia has a version control system, so in that sense it ''supports'' file versioning. Our requirement is ''keep all files from all contributors easily accessible, time stamped, and downloadable at any time without risk of data loss and without merge conflicts - while requiring only widely-accessible skill levels for team coordination.''' I think mediawiki does a better job at this problem statement, because you can see all the people working on the issue readily in the history. Further, our use of [[Visual Version History]] and CAD Part Libraries allows for quick visual diffs, where ready visual diffs would be much more difficult as they would be sread throughout many developers' accounts until they are committed to master. Navigating version histories is readily accessible to novices, whereas Github is pretty much for power users.
#'''Robustness''' - Counterargument: yes, robustness in software, but it is not robust for open hardware development. For example, it can't handle video. So in terms of robustness, Git is less robust for handling a more complex process of hardware dev, for an integrated process like OSE uses. But certainly it's more robust for software, and we should use Git for software.
#'''Data Replication''' - The same is effectively true for the wiki, because every collaborator has a copy of the files they are working on. I would argue that Data Replication is not possible for hardware - as for hardware, the whole project is terabytes (from videos and heavy assets such as large CAD assemblies). This is why a wiki-centric infrastructure is good. So this points to defining the problem statement clearly: Git is good for software, not for hardware. The initial qeustion is: why use wiki version history? The second question that we are asking, why use wiki for project management as opposed to git. Having specified the question, we can answer: we use wiki for overall development, we use git for software only, as a general best practice.
#'''Versions have a hash Key''' - wiki has the equivalent functionality of a hash key.
#'''Access control''' - The [[GVCS]] (creating a new infrastructure for civilization) is a broader project, therefor we allow everybody in without the need for a access control. The only question is spam, which we address by manual approval of new users.
#'''Accidental Overwrites'''- I'm not aware that this is an issue. If there is a submission conflict, that is clear to the submitter - their upload fails, and they upload a file again. If 100 people do this, they just try again and the upload should be reconciled in seconds. But there is never typically a large number of people working on a single file, as we normally coordinate so that if there are multiple people working, we work on different files, or break the file into smaller parts for multiple people to work on them. Further, we also encourage people to use their work log as a repo, and add to the main trunk at a later date. Accidental overwrite can be an issue for page edits - but not for file uploads. For page edits, we use embedded documents, which are crowd-collaborative-realtime-editable and never suffer from 'submit' conflicts.

==Continued Argumentation==
#'''Versions have a hash Key''' - wiki has the equivalent functionality of a hash key.
## I don't think that this is true. The problem with the wiki is that the latest version does not really have a hash, older versions can be linked to, but the newest version always has the same link, there is no permanent link. Or is there a way to address the current link for the future?

=Discussion=

I agree that given that you are using a wiki as a repository you would want to just upload a new version of a file and use it. I just think that MediaWiki was not intended to be used as a repository.

If I understand correctly the reason you gave for not using Git are

# You don't control the data with Gitlab
# Visual Version History
# Collaboration on a scale
# It is currently used for a large set of parts (this was not included originally but I think it is important)

I still think Git has major advantages and want to give counterpoints to the arguments above

== 1. You don't control the data with Gitlab ==

Q: I don't understand this, why don't you own the data, you can host it on your server.

A: Then why not just use our server? This means that we're hosting the data in 2 places, so why not just host it on our servers? And if Gitlab decides to end service, we have to have a local backup. Or if it changes its interface or usage terms, we may have to rework significant parts of our workflow. We need absolute control of our data as we are a long-term project.

== 2. Visual Version History ==

Q. I think that Visual Version History should not be a problem, you can either just continue using the wiki and then link to the git files. Even better, the visual version history could be automatically created as a commit hook and on GitLab.

A. Could be created: a visual gallery like in the wiki, but it already exists in Mediawiki so why reinvent the wheel? The wiki already has all the formatting to make this easy. And we don't want to require people understanding how to use Git platforms, which is a higher learning curve than a wiki.

== 3. Collaboration at a scale ==

Q: I think there is a case that the access privileges are much better with Git. I believe that pull requests are probably necessary on a very large scale collaboration.

A: That is specific to software workflows. In hardware workflows, authority is more distributed. The builder has ultimate authority. A software platform of Git relies on commits and commit control. A hardware platform needs to rely on 'non-commits'. I mean that every design is valid until it is tested. Because there is no uniform compiler in hardware, or it is more expensive to 'compile' or build - much work by default remains non-reconciled or 'un-committed' - as a potential viable fork. So in summary, hardware by its nature requires no access privileges - as decision-making (on commits or reconciliatiuon) is much more distributed in hardware. Ie, the guy in Africa, North Pole, Europe, and rural american town all need equal access - and whoever builds, decides. So permissions are simple: all source is open, and any build is an effective fork. So it seems that the workflow from software is the general idea, but in practice - the practices are subtly different. Specifically: you don't need access privileges - default is all open and the builder is the actual committer. You can't assign roles and privileges in hardware - it doesn't make sense.

== 4. It is currently used for a large set of parts ==

Q: I think this point is very strong and that the transition could be a lot of work. But I still think that it could be worth it, and it should be tried out.

A: Qeustion 3 implies that the problem statement is not reconciliation (commits). It's more about who puts up the effort to build. Yes, we can all collaborate on digital design and treat it like software - ie, someone takes the control of commits. Because you cannot pre-allocate the commit-control role, you cannot scale in the same way in hardware as in software.

Pizzooid Log

2021-02-10T16:14:25Z

Pizzooid:

== Wed Feb 10, 2021 ==
Setup [[OSE Linux]] USB Drive.

== Sat Feb 6, 2021 ==
[[Talk:The Case for Using Wiki Version History]]

Talk:The Case for Using Wiki Version History

2021-02-08T18:45:23Z

Pizzooid: /* Major Advantages */

Talk:The Case for Using Wiki Version History

2021-02-08T18:43:43Z

Pizzooid: /* Major Advantages */

Talk:The Case for Using Wiki Version History

2021-02-08T18:43:00Z

Pizzooid: /* Major Advantages */

Talk:The Case for Using Wiki Version History

2021-02-08T18:40:29Z

Pizzooid:

Wiki Log

2021-02-07T16:22:29Z

Pizzooid: Trying to reproduce

This is a log of wiki issues, performance, improvements, organization, and other issues related to the effective functioning of the wiki. See [[OSE Wiki Bugs]] and [[Wiki Issues]].

Other pages to see:
*[[Wiki Maintenance]]
*[[OSE Wiki Management]]
*[[OSE Wiki]]

=Thu Feb 4, 2021=

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000#2" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

Trying to reproduce the error on [[File:VersionBug.fcstd]]

[[User:Pizzooid]] was not able to reproduce the error:
Steps tried to reproduce:

# Upload version
# Download version
# Upload new version
# Download new version

the new version is correctly downloaded on my computer. Is this different on your end?

=Sat Oct 17, 2020=
Saving SVGs doesn't work -

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

=Thu Dec 27, 2018=
*Check out this interesting bug - the picture is not updating when new version of a picture is uploaded. The next to last picture is the latest one - but the image that shows up shows the older picture:

[[File:noupdate.png|400px]]

=Wed May 23, 2018=
*Mass Delete in special pages - for mass delete of spam by one user
*Use the User:Name and Tools: email this user to contact users

=Thu Feb 2, 2017=
==Wiki Outstanding Items==
*Get proper sidebar on new wiki
*Speed up wiki response
*Get main page up
*Approve users manually
*Learn how to navigate between instructionals view and regular wiki view
*After all formatting is done - first update database for last time - and swith DNS record at Dreamhost

==Main OSE blog, Factor e Farm, Opensourcewarehouse.org, old Forum==
*Other databases have different logins - fef wp site, opensourcewarehouse wp, old forum in vanilla
*wp-config.php has the password info to find other databases -
*localsettings.php has initial settings for wiki software. We had that password already. Read only vs. write only login was shown.

We got so far as to getting the database for the fef site, by extracting password from the wp-config. We copied to new Hetzner. We archived also the entire fef wordpress database file and working directory into one archive and moved it to the new Hetzner.

Next steps are to move main ose wordpress, and the opensourcewarehouse.org wp database. And finally look up old forum database password, and then move that.

Ok. Bye.

Let's fix up the new Hetzner - how to make it look good.

=Tue Feb 23, 2016=
Changing license information at bottom of page from 3 to 4:

Marcin;

1. Log onto the server via ssh (assuming that you have the hetzner key in your .ssh folder, named as shown below):
$ ssh -i ~/.ssh/id_rsa-hetzner -p 222 -l osemain dedi978.your-server.de

2. Change to the "public_html/w" folder and edit the file "LocalSettings.php":
osemain@dedi978:~ cd public_html/w
osemain@dedi978:~$ nano LocalSettings.php
3. Change the text from 3.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/3.0/";
$wgRightsText = "CreativeCommons by-sa3.0";
to 4.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/4.0/";
$wgRightsText = "CreativeCommons by-sa4.0";
I just changed it for you using the steps above.

=Wed Dec 3, 2015=
Need to enable email capture from wiki registrations. Currently, the email is lost after registration is approved.

=Mon Sep 21, 2015=
Larger than 50MB files can't be uploaded still - trying the [[Cold Saw]] zipped CAD file upload.

=Thu Sep 10, 2015=
Marcin;

It appears to delete all attachments after the user account is confirmed, by an automated maintenance script.

In the database, it holds a record of the file while the account is pending, but afterward, there is nothing about it in the database.

I haven't found where it keeps the files meanwhile. It appears to encrypt the file name, as I see two values for its name, but not the file itself:
82a8f59a58588754c6ac4a8016c581ee3d37703f.pdf
and
150622_CV_EN.pdf
The weird thing is that when I click on the file name "150622_CV_EN.pdf", it somehow finds it. Weird.

Tom

=Thu Sep 3, 2015=
Example - http://opensourceecology.org/wiki/User:Pcharwood - upon registration, his resume - I clicked on it - and got it. But the second time I clicked on it, it was a bad link - http://opensourceecology.org/w/index.php?title=Special:ConfirmAccounts/authors&file=01ef55cbe8049485974417e742b372eeb73612df.pdf .

=Sat Aug 29, 2015=
Account registration fields - where to find them? When a person registers, there are other fields filled in, such as contact info. How to find this once a user is approved? Further, the uploaded CV - when clicked upon - it was a broken link but link was blue. Status: not resolved.

=Sat Aug 22, 2015=
Are [[Terms of Service]] visible upon a person registering? This refers to a Contributor Agreement. With this said - how do we find a person's profile and CV that they submit upon registration? That is critical to Wiki Culture and Collaborative Literacy. Status: not resolved

=Fri Aug 14, 2015=
Had an error - [[Image:wikierror.png|thumb]] - and Tom fixed it. He set the upload directory to the same as the photo upload directory. BTW: This setting is made in the file: /usr/home/osemain/public_html/w/includes/DefaultSettings.php. "I also document my changes in the file with the original lines intact so they can easily be returned to original settings."

[[Category:Logs]]

File:VersionBug.fcstd

2021-02-07T16:17:12Z

Pizzooid: Pizzooid uploaded a new version of File:VersionBug.fcstd

File:VersionBug.fcstd

2021-02-07T16:16:34Z

Pizzooid:

Wiki Log

2021-02-07T16:15:45Z

Pizzooid: /* Thu Feb 4, 2021 */

This is a log of wiki issues, performance, improvements, organization, and other issues related to the effective functioning of the wiki. See [[OSE Wiki Bugs]] and [[Wiki Issues]].

Other pages to see:
*[[Wiki Maintenance]]
*[[OSE Wiki Management]]
*[[OSE Wiki]]

=Thu Feb 4, 2021=

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000#2" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

Trying to reproduce the error on [[File:VersionBug.fcstd]]

=Sat Oct 17, 2020=
Saving SVGs doesn't work -

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

=Thu Dec 27, 2018=
*Check out this interesting bug - the picture is not updating when new version of a picture is uploaded. The next to last picture is the latest one - but the image that shows up shows the older picture:

[[File:noupdate.png|400px]]

=Wed May 23, 2018=
*Mass Delete in special pages - for mass delete of spam by one user
*Use the User:Name and Tools: email this user to contact users

=Thu Feb 2, 2017=
==Wiki Outstanding Items==
*Get proper sidebar on new wiki
*Speed up wiki response
*Get main page up
*Approve users manually
*Learn how to navigate between instructionals view and regular wiki view
*After all formatting is done - first update database for last time - and swith DNS record at Dreamhost

==Main OSE blog, Factor e Farm, Opensourcewarehouse.org, old Forum==
*Other databases have different logins - fef wp site, opensourcewarehouse wp, old forum in vanilla
*wp-config.php has the password info to find other databases -
*localsettings.php has initial settings for wiki software. We had that password already. Read only vs. write only login was shown.

We got so far as to getting the database for the fef site, by extracting password from the wp-config. We copied to new Hetzner. We archived also the entire fef wordpress database file and working directory into one archive and moved it to the new Hetzner.

Next steps are to move main ose wordpress, and the opensourcewarehouse.org wp database. And finally look up old forum database password, and then move that.

Ok. Bye.

Let's fix up the new Hetzner - how to make it look good.

=Tue Feb 23, 2016=
Changing license information at bottom of page from 3 to 4:

Marcin;

1. Log onto the server via ssh (assuming that you have the hetzner key in your .ssh folder, named as shown below):
$ ssh -i ~/.ssh/id_rsa-hetzner -p 222 -l osemain dedi978.your-server.de

2. Change to the "public_html/w" folder and edit the file "LocalSettings.php":
osemain@dedi978:~ cd public_html/w
osemain@dedi978:~$ nano LocalSettings.php
3. Change the text from 3.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/3.0/";
$wgRightsText = "CreativeCommons by-sa3.0";
to 4.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/4.0/";
$wgRightsText = "CreativeCommons by-sa4.0";
I just changed it for you using the steps above.

=Wed Dec 3, 2015=
Need to enable email capture from wiki registrations. Currently, the email is lost after registration is approved.

=Mon Sep 21, 2015=
Larger than 50MB files can't be uploaded still - trying the [[Cold Saw]] zipped CAD file upload.

=Thu Sep 10, 2015=
Marcin;

It appears to delete all attachments after the user account is confirmed, by an automated maintenance script.

In the database, it holds a record of the file while the account is pending, but afterward, there is nothing about it in the database.

I haven't found where it keeps the files meanwhile. It appears to encrypt the file name, as I see two values for its name, but not the file itself:
82a8f59a58588754c6ac4a8016c581ee3d37703f.pdf
and
150622_CV_EN.pdf
The weird thing is that when I click on the file name "150622_CV_EN.pdf", it somehow finds it. Weird.

Tom

=Thu Sep 3, 2015=
Example - http://opensourceecology.org/wiki/User:Pcharwood - upon registration, his resume - I clicked on it - and got it. But the second time I clicked on it, it was a bad link - http://opensourceecology.org/w/index.php?title=Special:ConfirmAccounts/authors&file=01ef55cbe8049485974417e742b372eeb73612df.pdf .

=Sat Aug 29, 2015=
Account registration fields - where to find them? When a person registers, there are other fields filled in, such as contact info. How to find this once a user is approved? Further, the uploaded CV - when clicked upon - it was a broken link but link was blue. Status: not resolved.

=Sat Aug 22, 2015=
Are [[Terms of Service]] visible upon a person registering? This refers to a Contributor Agreement. With this said - how do we find a person's profile and CV that they submit upon registration? That is critical to Wiki Culture and Collaborative Literacy. Status: not resolved

=Fri Aug 14, 2015=
Had an error - [[Image:wikierror.png|thumb]] - and Tom fixed it. He set the upload directory to the same as the photo upload directory. BTW: This setting is made in the file: /usr/home/osemain/public_html/w/includes/DefaultSettings.php. "I also document my changes in the file with the original lines intact so they can easily be returned to original settings."

[[Category:Logs]]

File:VersionBug.png

2021-02-07T16:14:19Z

Pizzooid: Pizzooid uploaded a new version of File:VersionBug.png

File:VersionBug.png

2021-02-07T16:12:22Z

Pizzooid: Pizzooid uploaded a new version of File:VersionBug.png

File:VersionBug.png

2021-02-07T16:12:04Z

Pizzooid: 1

Wiki Log

2021-02-07T16:11:46Z

Pizzooid: /* Thu Feb 4, 2021 */

This is a log of wiki issues, performance, improvements, organization, and other issues related to the effective functioning of the wiki. See [[OSE Wiki Bugs]] and [[Wiki Issues]].

Other pages to see:
*[[Wiki Maintenance]]
*[[OSE Wiki Management]]
*[[OSE Wiki]]

=Thu Feb 4, 2021=

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000#2" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

Trying to reproduce the error on [[File:VersionBug.png]]

=Sat Oct 17, 2020=
Saving SVGs doesn't work -

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

=Thu Dec 27, 2018=
*Check out this interesting bug - the picture is not updating when new version of a picture is uploaded. The next to last picture is the latest one - but the image that shows up shows the older picture:

[[File:noupdate.png|400px]]

=Wed May 23, 2018=
*Mass Delete in special pages - for mass delete of spam by one user
*Use the User:Name and Tools: email this user to contact users

=Thu Feb 2, 2017=
==Wiki Outstanding Items==
*Get proper sidebar on new wiki
*Speed up wiki response
*Get main page up
*Approve users manually
*Learn how to navigate between instructionals view and regular wiki view
*After all formatting is done - first update database for last time - and swith DNS record at Dreamhost

==Main OSE blog, Factor e Farm, Opensourcewarehouse.org, old Forum==
*Other databases have different logins - fef wp site, opensourcewarehouse wp, old forum in vanilla
*wp-config.php has the password info to find other databases -
*localsettings.php has initial settings for wiki software. We had that password already. Read only vs. write only login was shown.

We got so far as to getting the database for the fef site, by extracting password from the wp-config. We copied to new Hetzner. We archived also the entire fef wordpress database file and working directory into one archive and moved it to the new Hetzner.

Next steps are to move main ose wordpress, and the opensourcewarehouse.org wp database. And finally look up old forum database password, and then move that.

Ok. Bye.

Let's fix up the new Hetzner - how to make it look good.

=Tue Feb 23, 2016=
Changing license information at bottom of page from 3 to 4:

Marcin;

1. Log onto the server via ssh (assuming that you have the hetzner key in your .ssh folder, named as shown below):
$ ssh -i ~/.ssh/id_rsa-hetzner -p 222 -l osemain dedi978.your-server.de

2. Change to the "public_html/w" folder and edit the file "LocalSettings.php":
osemain@dedi978:~ cd public_html/w
osemain@dedi978:~$ nano LocalSettings.php
3. Change the text from 3.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/3.0/";
$wgRightsText = "CreativeCommons by-sa3.0";
to 4.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/4.0/";
$wgRightsText = "CreativeCommons by-sa4.0";
I just changed it for you using the steps above.

=Wed Dec 3, 2015=
Need to enable email capture from wiki registrations. Currently, the email is lost after registration is approved.

=Mon Sep 21, 2015=
Larger than 50MB files can't be uploaded still - trying the [[Cold Saw]] zipped CAD file upload.

=Thu Sep 10, 2015=
Marcin;

It appears to delete all attachments after the user account is confirmed, by an automated maintenance script.

In the database, it holds a record of the file while the account is pending, but afterward, there is nothing about it in the database.

I haven't found where it keeps the files meanwhile. It appears to encrypt the file name, as I see two values for its name, but not the file itself:
82a8f59a58588754c6ac4a8016c581ee3d37703f.pdf
and
150622_CV_EN.pdf
The weird thing is that when I click on the file name "150622_CV_EN.pdf", it somehow finds it. Weird.

Tom

=Thu Sep 3, 2015=
Example - http://opensourceecology.org/wiki/User:Pcharwood - upon registration, his resume - I clicked on it - and got it. But the second time I clicked on it, it was a bad link - http://opensourceecology.org/w/index.php?title=Special:ConfirmAccounts/authors&file=01ef55cbe8049485974417e742b372eeb73612df.pdf .

=Sat Aug 29, 2015=
Account registration fields - where to find them? When a person registers, there are other fields filled in, such as contact info. How to find this once a user is approved? Further, the uploaded CV - when clicked upon - it was a broken link but link was blue. Status: not resolved.

=Sat Aug 22, 2015=
Are [[Terms of Service]] visible upon a person registering? This refers to a Contributor Agreement. With this said - how do we find a person's profile and CV that they submit upon registration? That is critical to Wiki Culture and Collaborative Literacy. Status: not resolved

=Fri Aug 14, 2015=
Had an error - [[Image:wikierror.png|thumb]] - and Tom fixed it. He set the upload directory to the same as the photo upload directory. BTW: This setting is made in the file: /usr/home/osemain/public_html/w/includes/DefaultSettings.php. "I also document my changes in the file with the original lines intact so they can easily be returned to original settings."

[[Category:Logs]]

Wiki Log

2021-02-07T16:07:21Z

Pizzooid: /* Thu Feb 4, 2021 */

This is a log of wiki issues, performance, improvements, organization, and other issues related to the effective functioning of the wiki. See [[OSE Wiki Bugs]] and [[Wiki Issues]].

Other pages to see:
*[[Wiki Maintenance]]
*[[OSE Wiki Management]]
*[[OSE Wiki]]

=Thu Feb 4, 2021=

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000#2" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

Trying to reproduce the error on [[File:VersionBug.txt]]

=Sat Oct 17, 2020=
Saving SVGs doesn't work -

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

=Thu Dec 27, 2018=
*Check out this interesting bug - the picture is not updating when new version of a picture is uploaded. The next to last picture is the latest one - but the image that shows up shows the older picture:

[[File:noupdate.png|400px]]

=Wed May 23, 2018=
*Mass Delete in special pages - for mass delete of spam by one user
*Use the User:Name and Tools: email this user to contact users

=Thu Feb 2, 2017=
==Wiki Outstanding Items==
*Get proper sidebar on new wiki
*Speed up wiki response
*Get main page up
*Approve users manually
*Learn how to navigate between instructionals view and regular wiki view
*After all formatting is done - first update database for last time - and swith DNS record at Dreamhost

==Main OSE blog, Factor e Farm, Opensourcewarehouse.org, old Forum==
*Other databases have different logins - fef wp site, opensourcewarehouse wp, old forum in vanilla
*wp-config.php has the password info to find other databases -
*localsettings.php has initial settings for wiki software. We had that password already. Read only vs. write only login was shown.

We got so far as to getting the database for the fef site, by extracting password from the wp-config. We copied to new Hetzner. We archived also the entire fef wordpress database file and working directory into one archive and moved it to the new Hetzner.

Next steps are to move main ose wordpress, and the opensourcewarehouse.org wp database. And finally look up old forum database password, and then move that.

Ok. Bye.

Let's fix up the new Hetzner - how to make it look good.

=Tue Feb 23, 2016=
Changing license information at bottom of page from 3 to 4:

Marcin;

1. Log onto the server via ssh (assuming that you have the hetzner key in your .ssh folder, named as shown below):
$ ssh -i ~/.ssh/id_rsa-hetzner -p 222 -l osemain dedi978.your-server.de

2. Change to the "public_html/w" folder and edit the file "LocalSettings.php":
osemain@dedi978:~ cd public_html/w
osemain@dedi978:~$ nano LocalSettings.php
3. Change the text from 3.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/3.0/";
$wgRightsText = "CreativeCommons by-sa3.0";
to 4.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/4.0/";
$wgRightsText = "CreativeCommons by-sa4.0";
I just changed it for you using the steps above.

=Wed Dec 3, 2015=
Need to enable email capture from wiki registrations. Currently, the email is lost after registration is approved.

=Mon Sep 21, 2015=
Larger than 50MB files can't be uploaded still - trying the [[Cold Saw]] zipped CAD file upload.

=Thu Sep 10, 2015=
Marcin;

It appears to delete all attachments after the user account is confirmed, by an automated maintenance script.

In the database, it holds a record of the file while the account is pending, but afterward, there is nothing about it in the database.

I haven't found where it keeps the files meanwhile. It appears to encrypt the file name, as I see two values for its name, but not the file itself:
82a8f59a58588754c6ac4a8016c581ee3d37703f.pdf
and
150622_CV_EN.pdf
The weird thing is that when I click on the file name "150622_CV_EN.pdf", it somehow finds it. Weird.

Tom

=Thu Sep 3, 2015=
Example - http://opensourceecology.org/wiki/User:Pcharwood - upon registration, his resume - I clicked on it - and got it. But the second time I clicked on it, it was a bad link - http://opensourceecology.org/w/index.php?title=Special:ConfirmAccounts/authors&file=01ef55cbe8049485974417e742b372eeb73612df.pdf .

=Sat Aug 29, 2015=
Account registration fields - where to find them? When a person registers, there are other fields filled in, such as contact info. How to find this once a user is approved? Further, the uploaded CV - when clicked upon - it was a broken link but link was blue. Status: not resolved.

=Sat Aug 22, 2015=
Are [[Terms of Service]] visible upon a person registering? This refers to a Contributor Agreement. With this said - how do we find a person's profile and CV that they submit upon registration? That is critical to Wiki Culture and Collaborative Literacy. Status: not resolved

=Fri Aug 14, 2015=
Had an error - [[Image:wikierror.png|thumb]] - and Tom fixed it. He set the upload directory to the same as the photo upload directory. BTW: This setting is made in the file: /usr/home/osemain/public_html/w/includes/DefaultSettings.php. "I also document my changes in the file with the original lines intact so they can easily be returned to original settings."

[[Category:Logs]]

Wiki Log

2021-02-07T16:05:27Z

Pizzooid: /* Thu Feb 4, 2021 */

This is a log of wiki issues, performance, improvements, organization, and other issues related to the effective functioning of the wiki. See [[OSE Wiki Bugs]] and [[Wiki Issues]].

Other pages to see:
*[[Wiki Maintenance]]
*[[OSE Wiki Management]]
*[[OSE Wiki]]

=Thu Feb 4, 2021=

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000#2" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

Trying to reproduce the error on [[Reproduce Version History Bug]]

=Sat Oct 17, 2020=
Saving SVGs doesn't work -

<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQwYrzOxHxcswlM5ru59pD9SkQADNWUulLT8CbkiF1Y95CXncahzJXbNiLawqFrD-CnGh6ZH2JlSret/embed?start=false&loop=false&delayms=3000" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

[https://docs.google.com/presentation/d/17ltqeD_fbalCTsOAeIAswShz6IAy248IWoIkYfmPyYE/edit#slide=id.g5c3be0ce2d_1_28 edit]

=Thu Dec 27, 2018=
*Check out this interesting bug - the picture is not updating when new version of a picture is uploaded. The next to last picture is the latest one - but the image that shows up shows the older picture:

[[File:noupdate.png|400px]]

=Wed May 23, 2018=
*Mass Delete in special pages - for mass delete of spam by one user
*Use the User:Name and Tools: email this user to contact users

=Thu Feb 2, 2017=
==Wiki Outstanding Items==
*Get proper sidebar on new wiki
*Speed up wiki response
*Get main page up
*Approve users manually
*Learn how to navigate between instructionals view and regular wiki view
*After all formatting is done - first update database for last time - and swith DNS record at Dreamhost

==Main OSE blog, Factor e Farm, Opensourcewarehouse.org, old Forum==
*Other databases have different logins - fef wp site, opensourcewarehouse wp, old forum in vanilla
*wp-config.php has the password info to find other databases -
*localsettings.php has initial settings for wiki software. We had that password already. Read only vs. write only login was shown.

We got so far as to getting the database for the fef site, by extracting password from the wp-config. We copied to new Hetzner. We archived also the entire fef wordpress database file and working directory into one archive and moved it to the new Hetzner.

Next steps are to move main ose wordpress, and the opensourcewarehouse.org wp database. And finally look up old forum database password, and then move that.

Ok. Bye.

Let's fix up the new Hetzner - how to make it look good.

=Tue Feb 23, 2016=
Changing license information at bottom of page from 3 to 4:

Marcin;

1. Log onto the server via ssh (assuming that you have the hetzner key in your .ssh folder, named as shown below):
$ ssh -i ~/.ssh/id_rsa-hetzner -p 222 -l osemain dedi978.your-server.de

2. Change to the "public_html/w" folder and edit the file "LocalSettings.php":
osemain@dedi978:~ cd public_html/w
osemain@dedi978:~$ nano LocalSettings.php
3. Change the text from 3.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/3.0/";
$wgRightsText = "CreativeCommons by-sa3.0";
to 4.0:
$wgRightsUrl = "http://creativecommons.org/licenses/by-sa/4.0/";
$wgRightsText = "CreativeCommons by-sa4.0";
I just changed it for you using the steps above.

=Wed Dec 3, 2015=
Need to enable email capture from wiki registrations. Currently, the email is lost after registration is approved.

=Mon Sep 21, 2015=
Larger than 50MB files can't be uploaded still - trying the [[Cold Saw]] zipped CAD file upload.

=Thu Sep 10, 2015=
Marcin;

It appears to delete all attachments after the user account is confirmed, by an automated maintenance script.

In the database, it holds a record of the file while the account is pending, but afterward, there is nothing about it in the database.

I haven't found where it keeps the files meanwhile. It appears to encrypt the file name, as I see two values for its name, but not the file itself:
82a8f59a58588754c6ac4a8016c581ee3d37703f.pdf
and
150622_CV_EN.pdf
The weird thing is that when I click on the file name "150622_CV_EN.pdf", it somehow finds it. Weird.

Tom

=Thu Sep 3, 2015=
Example - http://opensourceecology.org/wiki/User:Pcharwood - upon registration, his resume - I clicked on it - and got it. But the second time I clicked on it, it was a bad link - http://opensourceecology.org/w/index.php?title=Special:ConfirmAccounts/authors&file=01ef55cbe8049485974417e742b372eeb73612df.pdf .

=Sat Aug 29, 2015=
Account registration fields - where to find them? When a person registers, there are other fields filled in, such as contact info. How to find this once a user is approved? Further, the uploaded CV - when clicked upon - it was a broken link but link was blue. Status: not resolved.

=Sat Aug 22, 2015=
Are [[Terms of Service]] visible upon a person registering? This refers to a Contributor Agreement. With this said - how do we find a person's profile and CV that they submit upon registration? That is critical to Wiki Culture and Collaborative Literacy. Status: not resolved

=Fri Aug 14, 2015=
Had an error - [[Image:wikierror.png|thumb]] - and Tom fixed it. He set the upload directory to the same as the photo upload directory. BTW: This setting is made in the file: /usr/home/osemain/public_html/w/includes/DefaultSettings.php. "I also document my changes in the file with the original lines intact so they can easily be returned to original settings."

[[Category:Logs]]

Pizzooid Log

2021-02-06T21:27:39Z

Pizzooid: Created page with "== Sat Feb 6, 2021 == Talk:The Case for Using Wiki Version History"

== Sat Feb 6, 2021 ==
[[Talk:The Case for Using Wiki Version History]]

Talk:The Case for Using Wiki Version History

2021-02-06T21:24:28Z

Pizzooid: Drawbacks of using MediaWIki as a repository

I agree that given that you are using a wiki as a repository you would want to just upload a new version of a file and use it. I just think that MediaWiki was not intended to be used as a repository.

If I understand correctly the reason you gave for not using Git are

# You don't control the data with Gitlab
# Visual Version History
# Collaboration on a scale
# It is currently used for a large set of parts (this was not included originally but I think it is important)

I still think Git has major advantages and want to give counterpoints to the arguments above

== 1. You don't control the data with Gitlab ==

I don't understand this, why don't you own the data, you can host it on your server.

== 2. Visual Version History ==

I think that Visual Version History should not be a problem, you can either just continue using the wiki and then link to the git files. Even better, the visual version history could be automatically created as a commit hook and on GitLab.

== 3. Collaboration at a scale ==

I think there is a case that the access privileges are much better with Git. I believe that pull requests are probably necessary on a very large scale collaboration.

== 4. It is currently used for a large set of parts ==

I think this point is very strong and that the transition could be a lot of work. But I still think that it could be worth it, and it should be tried out.

Collaborative Literacy

2021-02-06T15:29:01Z

Pizzooid:

I first found out that the term ''collaborative literacy'' was ''a thing'' from http://fasterthan20.com/.
The word Collaborative Literacy wants to convey that collaboration is a learned skill i.e. a literacy.

=2020=
Collaborative Literacy session from quarantine during the New Zealand Open Source Microfactory STEAM Camp:

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/D9jSo-p0bQM" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></html> .

=2019=
==Discussion with Eugene Kim==

Eugene is a seminal thinker in the field of Collaborative Literacy.

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/frbz2bpLCsA" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></html>

Last 17 minutes:

<html><iframe width="300" height="200" src="https://www.youtube.com/embed/2SzoJQkIH88" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></html>

==Open Source Microfactory Startup Camp on Collaborative Literacy==
<html><iframe width="560" height="315" src="https://www.youtube.com/embed/LMDMXUt6Xkk" frameborder="0" allow="accelerometer; </nowiki>autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></html>

=Key Tenet for OSE Applications=

'''The key tenet of collaborative literacy is that if everyone who wanted to make a better world could collaborate to make a better world for just one day, we would solve all the pressing world issues by tomorrow.'''

Stated in another way - if every person in the world would contribute just one hour in a single year to open source all of the world's knowledge, we would be done with all the R&D for OSE in one hour.

This recognition must be kept in mind as we go about solving all the pressing world issues.

The challenge - is coordination of effort.

In an incentive challenge - assuming that a prize grabs the world's attention - it is then the collaboration architecture that must be developed.

= Collaborative Literacy Webinar =
See the overview presentation on collaboration goals of OSE - and what it means to collaborate effectively.

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/videoseries?list=PL6Jpysxw3Ty--ILAxCWI5DRFFFvH4KzXW" frameborder="0" allowfullscreen></iframe></html>

=Principles and Procedures=
OSE is a project that follows certain standard procedures to enhance collaboration and Economic [[Time Binding]]:
#Publish early and often.
#If it is worth doing at all, it is worth doing badly.
#Publish on the wiki. The wiki is publicly viewable and editable, therefore anyone can have access to what you publish. If you send that information to a single person, then you have reached only a small fraction of your potential audience. Because we value open access to information, and because we have open boundaries to participation - publishing on the wiki is preferable to sending emails.
#Our near and long term goal is virally replicable, open source enterprise following the principles of Economic Time Binding. The social contract on Campus focuses around this.
#We are building a Construction Set, not a single product. If you like to think of a 'single product', that product is the entire Set.
#Subject matter expert, open source contributors lead the way. The project focuses on identifying and recruiting such contributors towards a greater goal than they could achieve themselves.
#Our methodology is open source, agile development.
#Our governance is based on meritocracy.
#We favor division of labor performed by multi-skilled generalists.
#Our human goal is to promote [[Integrated Humans]] who are aware of [[Self-Determination Theory]].
#We believe that the most effective road towards peacekeeping is effective production. Progressive military people also believe this.
#We like to create tools. A tool can be used for good or evil. We are interested in tools that lead to regenerative development.
#We believe in [[8 Forms of Capital]] plus the ninth one, Open Source Capital - defined as the wealth that comes from pursuing [[Distributive Enterprise]]
#We do not invent anything new. We study industry standards and build upon them to innovate on integrated, open source variants.
#We believe in a low-risk approach of building upon known solutions, rather than chasing for exotic new ones, because known solutions are sufficient to produce regenerative development at a modern standard of living.
#The proof of concept of the Global Village Construction Set is to demonstrate that a community of a dozen open source individuals can attain a modern standard of living using appropriate open source technology, up metal smelting and semiconductor production, from any parcel of land that has rocks, sunlight, plants, soil, and water.

=OSE Development Best Practices=
See [[OSE Collaboration Protocol]].

=Links=
*http://fasterthan20.com/
*[[Psychology of Non-Collaboration]]
*OBI Webinar on Collaborative Literacy - [[Collaborative Literacy 101: How to Work Effectively in an Open Source Hardware Movement]]
*Collaborative Literacy in Synthetic Biology - Eric - [[https://algalsyntheticbiology.com/2019/03/05/collaborative-literacy-for-distributed-synthetic-biology-mindsets-skills-and-habits/]]

[[Category:Collaboration Architecture]]

Collaborative Literacy

2021-02-06T15:28:37Z

Pizzooid:

I first found out that the term ''collaborative literacy'' was ''a thing'' from http://fasterthan20.com/.
The word Collaborative Literacy wants to convey that collaboration is a learned skill.

=2020=
Collaborative Literacy session from quarantine during the New Zealand Open Source Microfactory STEAM Camp:

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/D9jSo-p0bQM" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></html> .

=2019=
==Discussion with Eugene Kim==

Eugene is a seminal thinker in the field of Collaborative Literacy.

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/frbz2bpLCsA" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></html>

Last 17 minutes:

<html><iframe width="300" height="200" src="https://www.youtube.com/embed/2SzoJQkIH88" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></html>

==Open Source Microfactory Startup Camp on Collaborative Literacy==
<html><iframe width="560" height="315" src="https://www.youtube.com/embed/LMDMXUt6Xkk" frameborder="0" allow="accelerometer; </nowiki>autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></html>

=Key Tenet for OSE Applications=

'''The key tenet of collaborative literacy is that if everyone who wanted to make a better world could collaborate to make a better world for just one day, we would solve all the pressing world issues by tomorrow.'''

Stated in another way - if every person in the world would contribute just one hour in a single year to open source all of the world's knowledge, we would be done with all the R&D for OSE in one hour.

This recognition must be kept in mind as we go about solving all the pressing world issues.

The challenge - is coordination of effort.

In an incentive challenge - assuming that a prize grabs the world's attention - it is then the collaboration architecture that must be developed.

= Collaborative Literacy Webinar =
See the overview presentation on collaboration goals of OSE - and what it means to collaborate effectively.

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/videoseries?list=PL6Jpysxw3Ty--ILAxCWI5DRFFFvH4KzXW" frameborder="0" allowfullscreen></iframe></html>

=Principles and Procedures=
OSE is a project that follows certain standard procedures to enhance collaboration and Economic [[Time Binding]]:
#Publish early and often.
#If it is worth doing at all, it is worth doing badly.
#Publish on the wiki. The wiki is publicly viewable and editable, therefore anyone can have access to what you publish. If you send that information to a single person, then you have reached only a small fraction of your potential audience. Because we value open access to information, and because we have open boundaries to participation - publishing on the wiki is preferable to sending emails.
#Our near and long term goal is virally replicable, open source enterprise following the principles of Economic Time Binding. The social contract on Campus focuses around this.
#We are building a Construction Set, not a single product. If you like to think of a 'single product', that product is the entire Set.
#Subject matter expert, open source contributors lead the way. The project focuses on identifying and recruiting such contributors towards a greater goal than they could achieve themselves.
#Our methodology is open source, agile development.
#Our governance is based on meritocracy.
#We favor division of labor performed by multi-skilled generalists.
#Our human goal is to promote [[Integrated Humans]] who are aware of [[Self-Determination Theory]].
#We believe that the most effective road towards peacekeeping is effective production. Progressive military people also believe this.
#We like to create tools. A tool can be used for good or evil. We are interested in tools that lead to regenerative development.
#We believe in [[8 Forms of Capital]] plus the ninth one, Open Source Capital - defined as the wealth that comes from pursuing [[Distributive Enterprise]]
#We do not invent anything new. We study industry standards and build upon them to innovate on integrated, open source variants.
#We believe in a low-risk approach of building upon known solutions, rather than chasing for exotic new ones, because known solutions are sufficient to produce regenerative development at a modern standard of living.
#The proof of concept of the Global Village Construction Set is to demonstrate that a community of a dozen open source individuals can attain a modern standard of living using appropriate open source technology, up metal smelting and semiconductor production, from any parcel of land that has rocks, sunlight, plants, soil, and water.

=OSE Development Best Practices=
See [[OSE Collaboration Protocol]].

=Links=
*http://fasterthan20.com/
*[[Psychology of Non-Collaboration]]
*OBI Webinar on Collaborative Literacy - [[Collaborative Literacy 101: How to Work Effectively in an Open Source Hardware Movement]]
*Collaborative Literacy in Synthetic Biology - Eric - [[https://algalsyntheticbiology.com/2019/03/05/collaborative-literacy-for-distributed-synthetic-biology-mindsets-skills-and-habits/]]

[[Category:Collaboration Architecture]]