Coordinate GSOC package proposals

[aethelwulffe]

WE have proposals and interest in the following areas (this list will be updated). Each proposal should result in a document posted in the approved manner. Discussion should be related to documentation relevant to the specific subject. Once clean proposal discussion topics are in place, and a PROJECT has been implemented for each proposal, this issue will be closed.

Calendar Module [remove and replace]. This involves the SMARTY removal to a great extent, but not completely. The proposals in this category should focus intently on the calendar related functions in isolation as much as possible. For other project proposal coordination, this one must have time set aside to maintain communications with other parties on:

• Status SMARTY component removal
• Function calls to the new calendar system that communication modules and other UI elements will require. *The API for the calendar should be published to other developers as a very early deliverable.

UI Redevelopment. This is not just a theme and validation package.

• This will (first) replace the SMARTY-dependent pieces. Generally these are functional and simple interfaces.
• The styling format of these replaced pieces should be used as the application-wide look and feel of where the user should expect to see controls, how they are named, and give other developers access via CSS themes to re-skin the whole project if they want to.
• Documentation. This project will be creating the standard that the instruction sets will be dependent on.
• Sample styling. Depending on the path that the proposal takes, this will either be central to the package scope, or a stretch to accomplish in addition to everything else, but a new theme, named something like "Liberation" or "Glory Road" or "GSOC" would be a good addition. We don't care if it invalidates all original themes (provided RTL functionality still exists), but excess, legacy, or duplicated styling controls should be renovated in a way that makes use of the CSS style easy for use by other developers. Comments on where samples of the style elements are used should be in the code or documentation, preferably with actual file and line references.

PDO upgrade. The below list is deceptively short. This is not a trivial project

• Early deliverable: Intended API for SQL made available to all other developers. This should include a crosswalk from the original query functions as working documentation.
• Installation process.
• Configuration process.
• Upgrade and Patch process.
• All functions in sql.inc.
• All function calls (or new connections) to any database in the application.

Please [MENTORS], edit this post to add or modify.

[azwreith]

@aethelwulffe I can't seem to decide between the Calendar and UI Re-development projects. They both seem so very attractive! :sob:

[pri2si17-1997]

@aethelwulffe Can you please explain removal of smarty engine? Does it mean to use framework or something else?

[aethelwulffe]

@pri2si17-1997 Meaning...we want to just use php or js (native) to display the various input forms that currently depend on the SMARTY template engine. There is nothing wrong per-se with using a template engine, but the code base does things in a hodge-podge fashion, using every widget that has ever hit the market. If we do decide to use a framework (minimalist bootstrap, or all the way laravel or something) then we need to do a major re-factor of the whole application and use ALL of the framework for everything everywhere. The idea is to simplify. Our version of SMARTY is indeed very old. It could be updated, sure, but only the calendar gets any real use out of it...which we need to replace. It is also a maintenance issue with having to clear the cache, or deal with compiled templates with 300 character-long names, and all sorts of write permissions etc... The idea is to do a search-and-destroy on anything that uses a smarty template, then recreate the features (like the administration/Practice settings) in some comprehensible fashion that does not require someone to be an expert on some framework (or Wordpress coding standards!) to figure out. When/if we go deep with some framework because it really will do something for us, by gum we will all learn that framework, pare it down to the components we actually need (and no others) and learn to use it to it's fullest extent. That time is not now. @azwreith Get to work refining that calendar proposal. You jumped on it, and everyone else went looking elsewhere...so stick with it. I (and the other GSOC candidates) are depending on you putting out a strong offering so that they can make compatible proposals (or perhaps just plagiarize yours 😸 ). Pare it down as narrowly as you can. The dream to do everything is understandable, but since I can already tell that you, Priyanshu and Nilesh are all leaders and good communicators, you guys are going to be running teams at some level. Myself, I have been fighting the idea that I am not Superman for...oh...probably the last 30-35 years. Hard-worker? yeah, sure. Genius? sure, why not. Superman? ...well, the record begs to differ. HINT: you aren't one either. The first person you supervise is always yourself. Learn to manage by making realistic goals (if optimistic). Make sure you can document those goals in a work-package that you could turn over to any other competent person at any point to complete. If you succeed there, your communication skills are where they need to be.

[aethelwulffe]

@pri2si17-1997 @nileshprasad137 Are either one of you interested in tackling PDO?

[pri2si17-1997]

@aethelwulffe

Yeah, I am interested and would like to work on PDO.

[aethelwulffe]

Well, I think I would enjoy seeing your proposal on that, and I strongly encourage Nilesh to hammer together a proposal to calm the hideous appearance of the application. I think both factors severely limit the project, and I am grateful that you mentioned PDO. I think I am going to have to launch a constellation of testing VM's to try to keep up.

[azwreith]

You got it, sir! I already removed all the extra non-calendar stuff from my proposal and now planing to go into real detail with the calendar. Yep I really wanna do everything, but you are right. I must set realistic expectations that I can achieve. So I'll do my best to set a timeline that is optimal and achievable!

[nileshprasad137]

@aethelwulffe Yes, I have worked with PDO before and am well versed with it. I would also like to say, that there would a month between the last date of submitting proposal and the announcement of results . We can already start to work on the revamp of UI which would make our work much easier. I have been going through Smarty Template's Documentation for trying to understand its functionality.

[nileshprasad137]

Also during that time, there would not be much academic workload, which could be highly useful for all of us. Till now, I have been taking up really small tasks , but now I think its the time to go deep.

[azwreith]

@nileshprasad137 You are so lucky man. I got my next month filled up with projects, lab exams and then end-sem exams. But yeh, even I would be sending as many PRs as I can now that my mid terms are done (yay!) :yum:

[nileshprasad137]

@azwreith No, not that lucky . But yeah ,less workload till 15th or 20th April.

[pri2si17-1997]

@azwreith you are right. Same is the case with me ;)

[aethelwulffe]

@pri2si17-1997 , I thought you were gonna hit PDO? You? Nilesh? We are restricted to one proposal per project/participant.

[pri2si17-1997]

Yes @aethelwulffe , I am going for that only.

[nileshprasad137]

@aethelwulffe Do you mean if @pri2si17-1997 is going for PDO , I should go for UI redevelopment?. See, I make myself clear here. I am comfortable with PDO as well as UI redev. I think we can submit multiple proposals to a single organisation and I can assure you that I have the time to write two proposals after Thursday of this week ,when my mid-term get over. Please don't misunderstand that I am running away from competition.

From GSOC Floss Manual , http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/

[aethelwulffe]

I got some bad info from the folks on the forum then.... Should have gone to the source! OK, free-for-all! fire away! -I ain't no competitor...just a survivor. I do the whole team thing when it comes to fighting.

[tmccormi]

What we can't do is have two people on the same project.

Tony McCormick

On Mar 20, 2017 8:07 PM, "Art Eaton" notifications@github.com wrote:

I got some bad info from the folks on the forum then.... Should have gone to the source! OK, free-for-all! fire away! -I ain't no competitor...just a survivor. I do the whole team thing when it comes to fighting.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LibreHealthIO/LibreEHR/issues/522#issuecomment-287881755, or mute the thread https://github.com/notifications/unsubscribe-auth/AARci_HWK-xdycPngSyTHF30UYU6Xqz4ks5rntx2gaJpZM4MhxgG .

-- Please be aware that e-mail communication can be intercepted in transmission or misdirected. Please consider communicating any sensitive information by telephone. The information contained in this message may be privileged and confidential. If you are NOT the intended recipient, please notify the sender immediately with a copy to hipaa-security@mrsb-ltd.com and destroy this message.

[azwreith]

I don't think we can submit more than one proposal to the same organization either

[pri2si17-1997]

Hello @aethelwulffe , can you please tell that is backward compatibility to be maintained? I mean do you guys still prefer to use php versions below 5.5 (viz 5.3)?

[aethelwulffe]

php7+ That is it.

[pri2si17-1997]

ok.. :+1:

[azwreith]

@aethelwulffe I just submitted my draft. Do take a look please! :smile:

[nileshprasad137]

@aethelwulffe Yes, take a look at my proposal too! :smiley:

[pri2si17-1997]

@aethelwulffe I have also submitted the proposal. Please do have a look at it :)

[ghost]

Hi folks. 😄 Just a reminder to please keep further discussions around GSoC student proposals on the main forums at https://forums.librehealth.io/c/community/gsoc so other potential students can see them, as well as for a clear overall status of all the LH potential GSoC projects. Thanks!

[robbyoconnor]

Also, apologize for the heavy-handedness @aethelwulffe

[nileshprasad137]

@aethelwulffe If you have some time, can you please clear whether the project i proposed is a valid project or not so that I could start working on the other proposal?

[aethelwulffe]

I have time today @nileshprasad137, and I will give you a review ASAP. I apologize that my work schedule is going to be completely slammed until after the 31st. At the same time, I have confidence that the participants here have developed enough familiarity with the project to make very valid proposals. I haven't seen any issues other than extent of scope.

[pri2si17-1997]

@aethelwulffe Please do look at my proposal also, so that if any change required then I can do that as I have my mid sems from 31st march.

[aethelwulffe]

@pri2si17-1997 @nileshprasad137 @azwreith I intended for that message to apply to everyone. Should have gone ahead and added full alerts. I hope you guys don't feel like you have been ignored. -I will see you on the forums (unless it goes down again).

[anupsunni]

Hi, This is Anup. Nice to meet you @pri2si17-1997, @nileshprasad137 and @azwreith . Sorry for joining late @aethelwulffe . I have not submitted a proposal yet but I intend to. Right now I am trying to understand the references and connections to the modified postnuke calendar. I am interested in the replacement of the calendar module.

Again hi all and sorry for joining late. I will catch up with you guys . @aethelwulffe is it ok if I take some more time to experiment, learn and play with the code and submit my proposal in 3 days?

Nice meeting all of you, Anup

[aethelwulffe]

Yes, just remember this repo issue is for basic coordination (meaning learning about the project and familiarization with our integration process/side projects), and all "official" types of material should be restricted to the forum or actual GSOC interfaces. And yes, it is great to meet you, and we hope to see you around here!

[anupsunni]

Got it!! @aethelwulffe

[aethelwulffe]

Final comment about me here: I am currently acting as the GSOC liaison for the EHR project by default (everyone is a bit slammed right now), and I myself will be recusing myself from voting on proposals (If I even get invited). I am hardly neutral at this point, because honestly, I would hire and work with any of you guys in my shop without hesitation (If I wasn't poor and out of work!).

[robbyoconnor]

@aethelwulffe -- don't abstain!

[aethelwulffe]

My job is to be everyone's friend and help as much as my stumbling butt can manage...which leaves me in an advisory role, and not a decision maker. Naturally, I will do that for the voting package members if they request as well, but I will leave the vote up to others.

[aethelwulffe]

This thread is history. (WooHoo!)