Re: GSoC Proposal: Rewrite key parts of MacPorts in Python

* Mojca Miklavec: > I would not dismiss the initial effort as a GSOC project as long as > the student can prove the competence to do some good work and > reasonable potential to stick with the project afterwards. The way I understand GSoC projects is that smaller, self-contained work is preferred

Re: GSoC Proposal: Rewrite key parts of MacPorts in Python

Hi, On Thu, 2 Apr 2020 at 20:37, Joshua Root wrote: > > I would say it's OK for a GSoC project to be completely original and > never discussed before; the problem with this one is just the scope. You > would need to spend the entire summer (if not more) just doing design in > order to do it right,

Re: GSoC Proposal: Rewrite key parts of MacPorts in Python

On 2020-4-3 04:52 , Jackson Isaac wrote: > Hi Ryan, > > Thanks for your valuable insights and I really appreciate the detailed > feedback. I didn't realize these things before and the efforts that > went into creating and maintaining such a great project. > > I sincerely apologize to the communit

Re: GSoC Proposal: Rewrite key parts of MacPorts in Python

Hi Ryan, On Thu, Apr 2, 2020 at 3:44 AM Ryan Schmidt wrote: > > On Apr 1, 2020, at 18:20, Ryan Schmidt wrote: > > > On Mar 31, 2020, at 16:14, Alex Ionkov wrote: > > > >> I submitted a proposal this year for rewriting parts of MacPorts in > >> Python. The eventual goal is to rewrite all of MacPo

Re: GSoC Proposal: Rewrite key parts of MacPorts in Python

* Ryan Schmidt: > [...] I would have hoped that GSoC would be used as an opportunity for > us to finally implement changes that we have wanted to do for years > but never got around to doing, rather than to propose new projects > whose ramifications have never been discussed before. Quite so. Not

Re: GSoC Proposal: Rewrite key parts of MacPorts in Python

On Apr 1, 2020, at 18:20, Ryan Schmidt wrote: > On Mar 31, 2020, at 16:14, Alex Ionkov wrote: > >> I submitted a proposal this year for rewriting parts of MacPorts in Python. >> The eventual goal is to rewrite all of MacPorts in Python to increase >> modularity and make integration of other API

Re: GSoC Proposal: Rewrite key parts of MacPorts in Python

On Mar 31, 2020, at 16:14, Alex Ionkov wrote: > I submitted a proposal this year for rewriting parts of MacPorts in Python. > The eventual goal is to rewrite all of MacPorts in Python to increase > modularity and make integration of other APIs with MacPorts easier. Is this an idea you just

Re: GSoC Proposal: Rewrite key parts of MacPorts in Python

I have no experience to gave you any valuable help on this Alex, just wanted to drop some ideas I have in mind.  I work in the frame of HPC computing and I’m a heavy user of spack (https://spack.readthedocs.io/en/latest/). It’s a package manager tailored for HPC that shares more than few featur

GSoC Proposal: Rewrite key parts of MacPorts in Python

Dear MacPorts community, I submitted a proposal this year for rewriting parts of MacPorts in Python. The eventual goal is to rewrite all of MacPorts in Python to increase modularity and make integration of other APIs with MacPorts easier. I've attached my proposal. As for some edits that have alr

GSoC Proposal: Enhancing the webapp

Dear Macports community, Last year during GSoC 19, I wrote the ports webapp under the mentorship of Mojca and Umesh, we had a functional app by the end of the GSoC period. The app still needs a lot of improvements- codebase needs to be improved so that new maintainers can start quickly, more featu

Re: Submitted the GSoC Proposal

Here's the link to the document by the way : A https://docs.google.com/document/d/1c2DkaHLueqMrY66n-l3nvHecVgsezD2XOR8iaF-kkH4/edit?usp=drivesdk On Tue, Mar 24, 2020, 4:04 AM Vibhansh Gupta wrote: > Hey everyone ! > > I finally submitted my proposal on the Google Sumer of Code website. > Please

Submitted the GSoC Proposal

Hey everyone ! I finally submitted my proposal on the Google Sumer of Code website. Please do let me know your thoughts on it, either on the Google Doc as comments or via mail. Either way, I will be grateful for any and for all of your thoughts and advice on it. I am super pumped to work and h

Re: GSoC Proposal

Hey, I really want to thank you guys for selecting me. I am really overjoyed and excited about working with you guys!:):) I will make sure to always put in my best efforts and to do the job I'm assigned to the best of my abilities. I look forward to an awesome summer, coding and getting to know t

Re: GSoC Proposal

Dear Karan, On Fri, 3 May 2019 at 23:27, Karan Sheth wrote: > > If PEAR ports are useful to the community then I would like to take > this as stretch goals / after GSoC goal. For anyone putting the GSOC mails to "ignore mode" due to heavy traffic ... maybe leave the comment inside https://git

Re: GSoC Proposal

Hey, So I came across this recent mail in mailing list[1] stating the PR for deletion of PHP PEAR ports. I went through a few of the ports and it seems that once the update functionality of UPT is completed the updation of these ports could be easily automated just by adding a PEAR frontend to upt

Re: Feedback Request for final GSoC Proposal [Speed Up Trace Mode]

Hi, Sorry for re-mailing. I know it's almost the last moment. But if possible, please provide any possible feedback. https://docs.google.com/document/d/14eSXwZ6N1vRcBudaJWlwO5G17dY5B1nHgfhh52tSnv0/edit# Regards, Mihir

Feedback Request for final GSoC Proposal [Speed Up Trace Mode]

Hi everyone, Kindly check my final proposal and provide any possible feedback. https://docs.google.com/document/d/14eSXwZ6N1vRcBudaJWlwO5G17dY5B1nHgfhh52tSnv0/edit# Regards, Mihir

Re: GSoC Proposal

Hey, Just a gentle reminder, If I could get a reply to my previous mail as the deadline for submission is now less than a day and I would like to submit the proposal well before the deadline. Sorry for remailing. Thanks, Karan Sheth On Mon, Apr 8, 2019 at 12:05 AM KARAN SHETH wrote: > > Hey, >

Re: GSoC Proposal

Hey, > There's nothing specific that I would want to comment on. > Well, to me it's not entirely clear how the automatic updates would be > supposed to work, but ... I made some changes to the update part, is it better now or am I still missing something? > And the stretch goals are somewhat sho

Re: GSoC Proposal

On Sat, 6 Apr 2019 at 13:54, KARAN SHETH wrote: > > I would also like to ask if anything else needs to be added or updated > in the proposal as the deadline is nearing. There's nothing specific that I would want to comment on. Well, to me it's not entirely clear how the automatic updates would be

Re: GSoC Proposal

On Sat, 6 Apr 2019 at 04:06, Cyril Roelandt wrote: > > Upt gives you three kinds of dependencies: build, runtime and test. This > should be done in the backend. MacPorts also splits "runtime" dependencies into two types. One are proper runtime dependencies (not needed for building the package itse

Re: GSoC Proposal

Hey, > Check your dependencies; this should only happen if your port does not > depend on the port that provides this file, i.e. python37. You might be > overwriting the dependency by setting depends_lib rather than appending > to it. Changing from this : if {${name} ne ${subport}} { depends

Re: GSoC Proposal

On 2019-4-6 11:01 , KARAN SHETH via macports-dev wrote: > One issue I faced while going over the checklist for PR is: > When I try installing upt with trace mode (-vst), it fails but other > than that it installs properly. > Any way to fix this issue? > > Error: > > ---> Building upt > Executing

Re: GSoC Proposal

Hello, On 2019-04-05 09:22, Renee Otten wrote: > this looks like a very good start! There are a few things that should be > changed and I listed them below (some of them common to all three ports): What could be interesting here is to improve upt to make sure we never witness these issues ever a

Re: GSoC Proposal

Hey, > 1) you’re missing the “license” field (you should have gotten a warning about > this when doing “port lint —nitpick py-upt”) > 2) the value for “homepage” seems incorrect > 3) since upt is a tool (i.e., run on the command line and not really used as > a library by other packages) only on

Re: GSoC Proposal

hi Karan, this looks like a very good start! There are a few things that should be changed and I listed them below (some of them common to all three ports): 1) you’re missing the “license” field (you should have gotten a warning about this when doing “port lint —nitpick py-upt”) 2) the value

Re: GSoC Proposal

On Fri, Apr 5, 2019 at 2:25 PM Mojca Miklavec wrote: > > On Fri, 5 Apr 2019 at 09:16, KARAN SHETH wrote: > > On Fri, Apr 5, 2019 at 11:59 AM Mojca Miklavec wrote: > > > > > > Dear Karan, > > > > > > No time to test now, but what does "port contents py37-upt" say? It > > > could be called upt-py37

Re: GSoC Proposal

On Fri, 5 Apr 2019 at 09:16, KARAN SHETH wrote: > On Fri, Apr 5, 2019 at 11:59 AM Mojca Miklavec wrote: > > > > Dear Karan, > > > > No time to test now, but what does "port contents py37-upt" say? It > > could be called upt-py37 or something. That's a weird consequence of > > supporting multiple ve

Re: GSoC Proposal

Hey, On Fri, Apr 5, 2019 at 11:59 AM Mojca Miklavec wrote: > > Dear Karan, > > No time to test now, but what does "port contents py37-upt" say? It > could be called upt-py37 or something. That's a weird consequence of > supporting multiple version of python at the same time. Port py37-upt contai

Re: GSoC Proposal

Dear Karan, On Fri, 5 Apr 2019 at 08:25, KARAN SHETH wrote: > > Hey, > > So I tried porting upt and in the process had to port spdx-lookup and spdx. > These are the portfiles for the same [1],[2],[3]. > > When I try to install upt there is no error message but while trying > to run upt via a term

Re: GSoC Proposal

Hey, So I tried porting upt and in the process had to port spdx-lookup and spdx. These are the portfiles for the same [1],[2],[3]. When I try to install upt there is no error message but while trying to run upt via a terminal directly it says the command not found whereas if I go to python consol

Re: GSoC Proposal

Hey, On Wed, Apr 3, 2019 at 2:35 AM Mojca Miklavec wrote: > > Dear Karan, > > you may put such statistics and suggestions for action plans in the proposal > (or appendix to proposal). Ok, I'll do that soon > What about pypackage -> py-pypackage? (I miss such entries on the list, > unless thos

Re: GSoC Proposal

Dear Karan, you may put such statistics and suggestions for action plans in the proposal (or appendix to proposal). What about pypackage -> py-pypackage? (I miss such entries on the list, unless those are the ones you intentionally didn't count.) Did you ignore capitalisation of names? Mojca On

Re: GSoC Proposal

Hey, Just to see how many ports will we have to rename if we take on this path I ran a quick script and following were the results: PyPI NameMacports NameNumber package package 10 package py-package 769 package

Re: Enabled commenting on GSoC Proposal

On Tue 2 Apr, 2019, 21:07 Mihir Luthra, <1999mihir.lut...@gmail.com> wrote: > >> Mihir, >> >> The proposal is view-only. You might need to give comment-access for >> us to leave feedback on the draft. >> >> Done > Try to avoid creating multiple mail threads. Thanks >

Enabled commenting on GSoC Proposal

> > > Mihir, > > The proposal is view-only. You might need to give comment-access for > us to leave feedback on the draft. > > Done

Re: GSoC Proposal

On Tue, 2 Apr 2019 at 01:33, KARAN SHETH wrote: > > Is it possible to rename the existing Python ports as per PYPI so that > issues of duplicates ports can be avoided? > Yes, I would be in favour of coming up with an "algorithm" for naming all python ports and then stick to it. Ports which don't

Re: GSoC Proposal

> I generated a portfile for py-upt and tried installing that after a few > manual edits, which will actually be automated in the future. > It did install properly without any errors but I guess there's some issue > with the path and because of which it was unuseable, once I figure this out > s

Re: GSoC Proposal

On 2019-04-01 11:39, Mojca Miklavec wrote: > Cyril: what's your desired destination for such work? I would suggest > placing the repositories on either > https://framagit.org/upt > or create a repository under > https://github.com/macports-gsoc > and do the pull request and code review on e

Re: GSoC Proposal

Hey, On Mon, Apr 1, 2019 at 8:34 PM Mojca Miklavec wrote: > On Mon, 1 Apr 2019 at 16:38, Renee Otten wrote: > > > > there is a figure showing a WebUI that is not described (personally I am > not sure if that would be needed anyway). > > My assumption was that Karan planned to submit "an alternat

Re: GSoC Proposal

Hey, On Mon, Apr 1, 2019 at 8:08 PM Renee Otten wrote: > hi Karan, Mojca, Cyril, > > > I am happy to help with testing and provide feedback. I quickly glanced > over the proposal draft and agree with what Cyril said; in addition, there > is a figure showing a WebUI that is not described (persona

Re: GSoC Proposal

Hey, On Mon, Apr 1, 2019 at 3:09 PM Mojca Miklavec wrote: > Dear Karan, > > Just a few quick notes (for others as well). > > On Sun, 31 Mar 2019 at 22:00, KARAN SHETH via macports-dev wrote: > > > > I have uploaded the project. > > Macports-Backend : https://github.com/Korusuke/upt-macports > >

Re: GSoC Proposal

Hey, I have completed most of the changes that you suggested. Haskell frontend has been now added to technical details and I guess I got why you were saying that why it would be tricky to add it as a frontend. Web UI has been removed seeing that it won't be a good add-on as suggested by Renne. Pl

Re: GSoC Proposal

On Mon, 1 Apr 2019 at 16:38, Renee Otten wrote: > > there is a figure showing a WebUI that is not described (personally I am not > sure if that would be needed anyway). My assumption was that Karan planned to submit "an alternative" proposal for another project (web app), but I might be wrong. M

Re: GSoC Proposal

hi Karan, Mojca, Cyril, I am happy to help with testing and provide feedback. I quickly glanced over the proposal draft and agree with what Cyril said; in addition, there is a figure showing a WebUI that is not described (personally I am not sure if that would be needed anyway). I agree tha

Re: GSoC Proposal

Dear Karan, Just a few quick notes (for others as well). On Sun, 31 Mar 2019 at 22:00, KARAN SHETH via macports-dev wrote: > > I have uploaded the project. > Macports-Backend : https://github.com/Korusuke/upt-macports > NPM-Frontend : https://github.com/Korusuke/upt-npm Awesome, thank you very

Re: GSoC Proposal

Hey, I will do the suggested changes and also add the pending stuff and then submit the draft proposal by tomorrow. Thanks for the review. Thanks, Karan Sheth On Mon, Apr 1, 2019 at 1:16 AM Cyril Roelandt wrote: > Hello, > > On 2019-04-01 00:30, KARAN SHETH wrote: > > I have started drafting m

Re: GSoC Proposal

: KARAN SHETH > > To: Cyril Roelandt > > Cc: "macports-dev@lists.macports.org" > > > > Subject: Re: GSoC Proposal > > Message-ID: > >9wlfhxv...@mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > &

Re: GSoC Proposal

Hello, On 2019-04-01 00:30, KARAN SHETH wrote: > I have started drafting my proposal for GSoC 2019. It would be great to > have a review on it before I submit the same. A few comments. First of all, "upt" is written in lower case, except when found at the beginning of a sentence :) To someone w

Re: GSoC Proposal

Thank Cyril! I have looked at your repository of upt and Mojca’s initial backend already; however, it would be helpful to be able to see the repository/commits of the GSoC student. > On Mar 31, 2019, at 2:50 PM, Cyril Roelandt > wrote: > > Hello, > > On 2019-03-31 13:26, Renee Otten wrote:

Re: GSoC Proposal

Hey, I have started drafting my proposal for GSoC 2019. It would be great to have a review on it before I submit the same. It's still a WIP, once done I will submit the same to GSoC draft proposal. Link: https://docs.google.com/document/d/1T0EItL09lk_oL36v6_BgvwRb_9E_FLKVdrOd-Nt8VYo/edit?usp=shar

Re: GSoC Proposal

Hello, On 2019-03-31 13:26, Renee Otten wrote: > where is your repository for this project? I wanted to take a look and > possibly provide some feedback specifically for the Python ports, but have a > hard time finding it… You may find the upt code and a lot of modules at https://framagit.org/u

Re: GSoC Proposal

ok and > possibly provide some feedback specifically for the Python ports, but have > a hard time finding it… > > Thanks, > Renee > > > > Date: Sat, 30 Mar 2019 15:46:28 +0530 > > From: KARAN SHETH > > To: Cyril Roelandt > > Cc: "macports-dev@lists.

Re: GSoC Proposal

ndt > Cc: "macports-dev@lists.macports.org" > > Subject: Re: GSoC Proposal > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Hey Cyril, > > I have made a merge request as you suggested, please review it if anything > is wrong. > > Thanks, > Karan Sheth

Re: GSoC Proposal

Hey Cyril, I have made a merge request as you suggested, please review it if anything is wrong. Thanks, Karan Sheth On Sat, Mar 30, 2019 at 4:16 AM Cyril Roelandt wrote: > On 2019-03-30 03:35, KARAN SHETH wrote: > > I had to update a bit of upt-cpan as it was not parsing description > properly

Re: GSoC Proposal

On 2019-03-30 03:35, KARAN SHETH wrote: > I had to update a bit of upt-cpan as it was not parsing description properly. Patches are welcome:) You can connect to https://framagit.org/upt/upt-cpan using your Github account, by the way. Cyril > Thanks, > Karan Sheth > > -- > >

Re: GSoC Proposal

On 2019-03-28 22:56, Mojca Miklavec wrote: > > Support for checksums has been implemented recently: > > https://framagit.org/upt/upt/commit/3f634370bbb80904411ff298d2b79e35c7591d23 > > Yes, the file would be downloaded and the checksum would be calculated, but > this would be done by upt (if som

Re: GSoC Proposal

Hey, On Mar 29 2019, at 3:26 am, Mojca Miklavec wrote: > > > master_sites git+https://github.com/request/request.git > > This line looks a bit suspicious. If the files live on github, we might want > to use the github PortGroup anyway, but let's leave that detail for later ... yeah the link was

Re: GSoC Proposal

On Thu, 28 Mar 2019 at 19:28, KARAN SHETH wrote: > Hey, > > [image: Sent from Mailspring] > On Thu, Mar 28, 2019 at 8:48 PM Mojca Miklavec wrote: > > > We are looking forward. I hope that Cyril will also help with the process > (my encounter with UPM so far was for the full two hours while hacki

Re: GSoC Proposal

Hey, On Thu, Mar 28, 2019 at 8:48 PM Mojca Miklavec mailto:mo...@macports.org)> wrote: > > We are looking forward. I hope that Cyril will also help with the process (my > encounter with UPM so far was for the full two hours while hacking on it :). I've written a basic npm frontend and macports ba

Re: GSoC Proposal

Dear Karan, On Thu, 28 Mar 2019 at 07:52, KARAN SHETH wrote: > Resending the mail cause, previous mail was not sent to mailing list. > On Wed, Mar 27, 2019 at 2:10 PM Mojca Miklavec wrote: > >> Dear Karan, >> >> I'm just answering a small part of your question here, a bit more about >> upt whil

GSoC Proposal

Resending the mail cause, previous mail was not sent to mailing list. On Wed, Mar 27, 2019 at 2:10 PM Mojca Miklavec wrote: > Dear Karan, > > I'm just answering a small part of your question here, a bit more about > upt while CC-ing its author & potential mentor: > > On Tue, 26 Mar 2019 at 18:15,

Re: GSoC Proposal

Dear Karan, I'm just answering a small part of your question here, a bit more about upt while CC-ing its author & potential mentor: On Tue, 26 Mar 2019 at 18:15, KARAN SHETH wrote: > > >> (Another option for a project in Python would be bringing universal >> packaging tool [1] to MacPorts.) >>

Re: GSoC Proposal

>> >> Warmly welcome to the MacPorts community! >> >> On Mon, 25 Mar 2019 at 20:36, KARAN SHETH via macports-dev wrote: >> >>> Hey there, >>> I would like to start by saying this is not GSoC Proposal as the >>> subject says but I had no idea

GSoC Proposal

Hey Mojca, Thanks for replying. On Tue, Mar 26, 2019 at 3:00 AM Mojca Miklavec wrote: > Dear Karan, > > Warmly welcome to the MacPorts community! > > On Mon, 25 Mar 2019 at 20:36, KARAN SHETH via macports-dev wrote: > >> Hey there, >> I would like to st

Re: GSoC Proposal

Dear Karan, Warmly welcome to the MacPorts community! On Mon, 25 Mar 2019 at 20:36, KARAN SHETH via macports-dev wrote: > Hey there, > I would like to start by saying this is not GSoC Proposal as the > subject says but I had no idea what else to call it. This is just to make >

GSoC Proposal

Hey there, I would like to start by saying this is not GSoC Proposal as the subject says but I had no idea what else to call it. This is just to make contact with you regarding a GSoC Project idea that I would really like to do. My name is Karan Sheth. I have attached a doc link wherein

Re: GSoC Proposal

Hi, On Thu, Apr 13, 2017 at 12:37:55AM +0200, Mojca Miklavec wrote: > I was talking to someone from the HB community. Apparently they tried > very hard to make Travis CI work. One of the major problems they had > other than the time limit (the builder is relatively slow and jobs get > killed after

Re: GSoC Proposal

On 4/12/17 10:37 PM, Mojca Miklavec wrote: I was talking to someone from the HB community. Apparently they tried very hard to make Travis CI work. One of the major problems they had other than the time limit (the builder is relatively slow and jobs get killed after 50 minutes, so any builds like

Re: GSoC Proposal

Hi, Just to clarify one thing (also to any other GSOC applicant): this discussion does not provide any indication about the ranking of the submitted proposal or whether this or any other proposal might be or not be accepted. There might be better or worse applications where less clarification is n

Re: GSoC Proposal

On 4/2/17 6:03 AM, Mojca Miklavec wrote: Thank you. Please include that into the proposal as well. It wasn't clear to me whether your project would be a full "replacement" compared to the current functionality of the buildbot or just covering some small load cycle (like doing very very basic chec

Re: GSoC Proposal

On 2 April 2017 at 04:23, Zero King wrote: > macOS VMs on Travis would do `port lint | tee lint.txt; if grep > "^Error: " lint.txt ; then ...` > > and `port install ...` (`port test ...` if test exists) and if one of them > failed Travis will report that back to GitHub. > > Also Travis will keep l

Re: GSoC Proposal

macOS VMs on Travis would do `port lint | tee lint.txt; if grep "^Error: " lint.txt ; then ...` and `port install ...` (`port test ...` if test exists) and if one of them failed Travis will report that back to GitHub. Also Travis will keep logs so lint results will be available there. On 4

Re: GSoC Proposal

Have you seen how homebrew does this? I imagine he means something like that: Every submission has to be submitted to the 10.10 - 10.12 bots first, to see if it builds. Every submission is suggested / required to have at least a minimal test `myport --version` to make sure something actually wo

Re: GSoC Proposal

Can you please elaborate a bit more on Travis CI will do lint and install tests on macOS 10.10-12 for PRs and commits. What does "install tests" refer to exactly? Mojca

Re: GSoC Proposal

> On Mar 31, 2017, at 6:21 PM, Zero King wrote: > > > On 3/31/17 6:23 PM, Rainer Müller wrote: >> First of all, great to see a proposal coming from you as a project member! > Thanks. >> We do not have anything else in Go yet, so this would be new to our >> infrastructure. I am a bit hesitant wi

Re: GSoC Proposal

On 3/31/17 6:23 PM, Rainer Müller wrote: First of all, great to see a proposal coming from you as a project member! Thanks. We do not have anything else in Go yet, so this would be new to our infrastructure. I am a bit hesitant with that, because even after this GSoC, we will need someone to

Re: GSoC Proposal

Hello, On 2017-03-31 17:43, Zero King wrote: > I'd like to implement a bot in Go dealing with pull requests for > macports-ports on GitHub and utilize Travis CI to test PRs and commits > in GSoC 2017. > > More details in my draft: > https://gist.github.com/l2dy/420533b821570e26dc7374898c3264fb >

Re: GSoC Proposal

Hi, On Fri, 31 Mar 2017 at 9:14 PM, Zero King wrote: Hi, I'd like to implement a bot in Go dealing with pull requests for macports-ports on GitHub and utilize Travis CI to test PRs and commits in GSoC 2017. More details in my draft: https://gist.github.com/l2dy/420533b821570e26dc7374898c3264fb

GSoC Proposal

Hi, I'd like to implement a bot in Go dealing with pull requests for macports-ports on GitHub and utilize Travis CI to test PRs and commits in GSoC 2017. More details in my draft: https://gist.github.com/l2dy/420533b821570e26dc7374898c3264fb Any advice is welcome and since this is a new id