Raring back to Leap: Trac .12 tracd Git to Trac 1.0.5 Apache modwsgi GitHub

[Joseph Thames]

Hello,

I'm seeking collaborators and advisors for a major open-source project, and possibly a new integrated Linux/Andoid client-server distro. I am based in Whidbey Island, WA, and I am ready for a major Linux client-server architecture upgrade for the project.

Here is the Linux C/S architecture now (connecting from WA clients to PA and TX servers):

Clients: TUOSA (Terminal USB OS Appliances) on HP dv6000 Pavilion laptops (uniform & cheap)

• Live USB boot sticks with Ubuntu 12.04 & Trinity 3.5.13 DE (KDE 3.5 forks)
• Remote NX/VNC connected to cloud VPS services (PA and TX)
• 20 KDE v-desktops with RHS strip-panel index pager for client/server desktop navigation
• Bottom KDE strip-panel used as task manager (complementing server-side)
  
• Trac 0.12 with tracd for wiki documentation

Servers: Automation labs for backend, OpenStack, and Web-IDE development work

• Ubuntu 12.04 Trinity 3.5.13 DE (duplicating client look & feel for integrated environment)
• Freenx connected to client TUOSA laptops enabling NX/VNC shared desktops
• 20 KDE v-desktops with LHS panel index pager for server & OpenStack navigation
• Top KDE panel used as task manager (complementing client-side)
  
• Perl-based rolling terminal menu-interface developer & user scaffolding (MIDUS)
• Designed for Android rolling-window compatibility & extensibility
• A scaffolding ramp above Unix CLI commands and Perl CLI virtual-commands
• Auto-annotated help systems via single-key-invoked Perl here documents
  
• Trac 0.12 tracd single environment with multiple Git repositories
  

I can supply client USB TUOSA sticks to collaborators and accounts on my servers so we can collaborate to create a new turnkey Linux/Android CS distro that will hopefully become a standard front-end for STEM education and garage-oriented scientific computing. I would prefer collaborators in the Seattle/Vancouver area, but I am not limiting participation worldwide.

Initial Task:

I want to first upgrade the Trac enviornment from 0.12 to the current stable Trac release and to standardize Git-based collaboration between VPS-local Git and GitHub. I need assistance and advice about this immediately. I tried to start the integration of local Git repos with GitHub while forking a new repo from GitHub. I also started shifting from tracd to Apache2 with modwsgi. But I was quickly reminded that this whole step needs to be carefully engineered.

I would prefer to hand-off this whole Linux/Android "CS penthouse" enviornment distro to a team of expert Trac-skilled SysAdmin designers and maintainers, so I can focus on the scientific application it was first designed to house.

Please start a dialog in this list with suggestions and advice,

Joseph "Bear" Thames - "beartham"

[Ryan Ollos]

Hello Joseph,

Within your message I see three major tasks:

1. Upgrade to Trac 1.0.x. 

2. Move from TracStandalone (tracd) to Apache

3. Integrate with GitHub.

(1) and (2) should be straightforward. There are some plugins to support (3), but whether GitHub integration can be readily accomplished depends on your requirements and evaluation of existing plugins.

In general I am very happy to help open source project use Trac. I am currently helping the jQuery/jQuery-UI team migrate their Trac infrastructure so I need to finish that before taking on more commitments. I may be able to help a few weeks down the road and I'm located in Seatle.

However, I'd first like to see some more details about your open source project. Is your Trac site publicly accessible? Can you post some links to your open source project so we can see in more detail what it is about, including the GitHub repository?

- Ryan

[Joseph Thames]

Hi Ryan,

I'm working to make the Trac site accessible, as it's Wiki explains this project. But it is partitioned between the client USB stick and the server. I'm merging the two wikis into the server version, which is accessible via the web. I haven't upgraded it in more than a year, so it will take a few days.

The first GitHub repo is a fork of a Modern-Perl web-IDE called Farabi, which I am calling NeoFront. I intend to re-purpose it as a browser-based IDE for NeoFortran, the new name for the successor to FortranCalculus77 which is the MetaCalculus successor to the PROSE modeling language, marketed in the mainframe time-sharing era, after its original development for Apollo.

I'm planning to release this whole 50-year Fortran advance into abstract modeling above and beyond calculus, to the open-source community. It involves "escalator" IDEs for compiler-compilers like Yacc and DParser, and GUI-builders like Glade2, Glade3, and GWT, plus AJAX-based "Spiritext", a tooltip-subhypertext used to self-document wiki-enhanced source code on the web.

These IDEs are wrappers around the front-end builders to automate the evolution of higher modeling media by end-user developers. They employ special Linux scaffolding to automate "round-trip engineering" which has mostly prevented evolution of higher modeling media by those diverse end-users capable of this level of subject-matter design. 

The acronym for this escalator IDE concept is ALAMEDA, for "assembly-line archive meld-editing development architecture". ALAMEDA scaffolding is a reversible design container and digestion process that maintains "meta-designs" in all stages between metaphoric (grammar and widgets) design and code design, using Perl here-documents in archive files.

NeoFortran is a mathematical analog of SQL, containing templates and iterative engines for optimization searching and simulation. As an non-interpretive native-code compiler system, it is a platform for lifting languages like Python to higher diversified modeling dialects, and GUIs like STELLA to even higher optimization-modeling levels which exploit parallel processing, but do not require parallel programming. The STELLA system-dynamics (SD) simulation motif overlaps differential-equations modeling in MetaCalculus, which extends SD into optimal-design and control (calculus of variations). And since STELLA technology is being introduced in kindergarten, the potential merger of these software technologies portends a uniform K-20 STEM modeling GUI medium.

The TUOSA Client/Cloud environment is an "AutoLab" container for all of this software apparatus, and I believe Trac is the best UI to facilitate its spread to DIY modeling-level end-users and SysAdmin/programmers as peer developers.

I will publish access to the Wiki in a few days. Subsequently it would be productive for you to visit me in my Clinton office near the ferry (9178 Hwy 525).

-Joseph

--
You received this message because you are subscribed to a topic in the Google Groups "Trac Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/trac-users/8U8J3c0xfzk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to trac-users+...@googlegroups.com.
To post to this group, send email to trac-...@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

[Joseph Thames]

Ryan,

You can access the TUOSA version of my Trac site at http://old32.metacalculus.net:8000/trac. This is probably the best intro of our proposed project, even though it is over a year old.

Presuming you can assist me with three tasks you outlined, some weeks in the future when you free up; I'm going to leave this task for now.  I need to focus on the refactoring of the GitHub fork, NeoFront, to repurpose it as the NeoFortran IDE. I will get back to you when I have that operational, hopefully by my first milestone date of June 23. Then I will be ready to push the refactoring mods up to GitHub, and start the integration work to ready the new Trac 1.0.5 for open-source collaboration.

-Joseph

--

Joseph 'Bear' Thames
MetaCalculus, LLC and Meta Science Foundation
(505) 977-9024 - Cell Phone
bear...@gmail.com

[RjOllos]

On Wednesday, May 20, 2015 at 4:18:18 PM UTC-4, Joseph Thames wrote:

Ryan,

You can access the TUOSA version of my Trac site at http://old32.metacalculus.net:8000/trac. This is probably the best intro of our proposed project, even though it is over a year old.

Presuming you can assist me with three tasks you outlined, some weeks in the future when you free up; I'm going to leave this task for now.  I need to focus on the refactoring of the GitHub fork, NeoFront, to repurpose it as the NeoFortran IDE. I will get back to you when I have that operational, hopefully by my first milestone date of June 23. Then I will be ready to push the refactoring mods up to GitHub, and start the integration work to ready the new Trac 1.0.5 for open-source collaboration.

I think at least 2 of the 3 tasks are possible. The ideal situation would be if someone on your team wanted to be mentored in Trac administration. I'm making a push to improve the Trac installation documentation and working directly with some end users that have moderate experience would help with that.  I intend to reshuffle / rewrite the documentation on configuring Trac to work with Apache and I think I can do a much better job with that if I can look over someone's shoulder that is following the process. My aim is to make the documentation much more accessible to someone with nothing more than basic system administration skills.

- Ryan