●● IRC: #techbytes @ Techrights IRC Network: Monday, January 20, 2025 ●● ● Jan 20 [04:44] schestowitz[TR2]
  • [04:44] schestowitz[TR2]
    How to Install Odoo ERP Software on Ubuntu 24.04 Server
    [04:44] schestowitz[TR2]
    [04:44] schestowitz[TR2]

    Odoo (formerly known as OpenERP) is a self-hosted suite of over 10,000 open Odoo is a free and open-source ERP solution for multiple types of businesses. Odoo formerly OpenERP is an ERP and CRM solution and beyond. It provides customer relationship management (CRM), sales pipeline, project management, manufacturing, invoicing, accounting, eCommerce, and many more.

    [04:44] schestowitz[TR2]

    Odoo is one of the complete ERP solutions for your business. It has 30 core modules by default and provides more than 4500 community modules to help your multiple businesses.

    [04:44] schestowitz[TR2]
    [04:44] schestowitz[TR2]
    • [04:44] -TechBytesBot/#techbytes-www.howtoforge.com | How to Install Odoo ERP Software on Ubuntu 24.04 Server ● Jan 20 [05:16] schestowitz[TR2]
  • [05:16] schestowitz[TR2]
    Ghostty Will Get You Excited About Using a Terminal Again
    [05:16] schestowitz[TR2]
    [05:16] schestowitz[TR2]

    That new terminal app is called Ghostty, and it was created by Mitchell Hashimoto, co-founder of HashiCorp. This new terminal is lightweight, fast, feature-rich and cross-platform.

    [05:16] schestowitz[TR2]

    Ghostty does things a bit differently. Where some terminal apps have a GUI feature for configuration, this one uses a flat text file that is loaded upon launch (or reloaded manually, when you make changes). For that reason alone, Ghostty isnt the ideal terminal for those just getting started with the command line. Instead, Ghostty is aimed at those with plenty of experience.

    [05:16] schestowitz[TR2]

    Thats not to say you cant use Ghostty with the default minimal configuration; you certainly can, but youd be missing out on a lot of features.

    [05:16] schestowitz[TR2]
    [05:16] schestowitz[TR2]
    • [05:16] -TechBytesBot/#techbytes-thenewstack.io | Ghostty Will Get You Excited About Using a Terminal Again - The New Stack ● Jan 20 [06:40] schestowitz[TR2] "" [06:40] schestowitz[TR2] Please find the full paper including our recommendations and some additional information here." [06:47] schestowitz[TR2] " [06:47] schestowitz[TR2] Thank you for our meeting of XX on objective setting / I have [06:47] schestowitz[TR2] considered the target that was set for me for 2025 / [OTHER [06:47] schestowitz[TR2] INTRODUCTION WHICH YOU ARE COMFORTABLE WITH]. [06:47] schestowitz[TR2] On [FILL IN DATE] my objectives were set at [FILL IN]. As in the past, [06:47] schestowitz[TR2] I commit to working to the best of my abilities in 2025. [06:47] schestowitz[TR2] However, with regard to the proposed objectives for 2025, I sincerely [06:47] schestowitz[TR2] regret having to inform you that I cannot commit to them. [06:47] schestowitz[TR2] I would like to point out the following: [06:47] schestowitz[TR2] - The objectives set correspond to an increase of [06:47] schestowitz[TR2] production/productivity of + [FILL IN] % compared to 2024. OR [06:47] schestowitz[TR2] The objectives set correspond to the additional supplementary [06:47] schestowitz[TR2] tasks: [LIST NEW TASKS YOU HAVE BEEN ASKED TO ACCOMPLISH]. [06:47] schestowitz[TR2] - These increases are not in line with the EPOs Financial Study [06:47] schestowitz[TR2] 2023, which plans a +2.1% increase/year/FTE in productivity in [06:47] schestowitz[TR2] order to keep a healthy financial and operational situation at [06:47] schestowitz[TR2] the EPO. I kindly request that my targets thus be reviewed to [06:47] schestowitz[TR2] the 2.1% productivity increase planned by the Financial Study. [06:47] schestowitz[TR2] - While I have nothing against challenging objectives by [06:47] schestowitz[TR2] definition, I consider it very important that my targets are [06:47] schestowitz[TR2] also achievable. This is especially true when I had no or only [06:47] schestowitz[TR2] little input in defining and setting my final objectives. [06:47] schestowitz[TR2] Achieving an objective requires a plan of how one intends to [06:47] schestowitz[TR2] arrive at the objectives. I can only note that no such plan has [06:47] schestowitz[TR2] been presented to and discussed with me and, in fact, no such [06:47] schestowitz[TR2] plan appears to exist. I am therefore left without any [06:47] schestowitz[TR2] instruction or guideline from you on how to achieve the 2025 [06:47] schestowitz[TR2] objectives. [06:47] schestowitz[TR2] - Therefore, my intention to work together with the team to achieve [06:47] schestowitz[TR2] good results finds its limits in my duty to adhere to the [06:47] schestowitz[TR2] requirements of the EPC and PCT, the decisions of the Enlarged [06:47] schestowitz[TR2] Board of Appeal, and the Guidelines for search and examination. [06:47] schestowitz[TR2] If I am expected to go beyond these limits, as is obviously [06:47] schestowitz[TR2] implied by the 2025 objectives, I kindly request a written plan [06:47] schestowitz[TR2] and corresponding written instructions on how to do so, so that [06:47] schestowitz[TR2] (1) the responsibility for the quality of products and the [06:47] schestowitz[TR2] consequences thereof will not be placed at my door, and (2) an [06:47] schestowitz[TR2] objective gap analysis can periodically be performed. [06:47] schestowitz[TR2] - The SP2028 mentions: putting the wellbeing of our people first [06:47] schestowitz[TR2] (p.17) and The EPO aims for a complete and accurate search [06:47] schestowitz[TR2] covering all aspects of the invention and a thorough written [06:47] schestowitz[TR2] opinion., (p.42). I do not see how I can reach the new targets [06:47] schestowitz[TR2] without compromising my health or the quality of the final [06:47] schestowitz[TR2] product. I therefore kindly request written instructions on how [06:47] schestowitz[TR2] to perform my tasks so that the responsibility for the quality [06:47] schestowitz[TR2] of my work and the consequences thereof will not be placed on [06:47] schestowitz[TR2] my shoulders. [06:47] schestowitz[TR2] 4 [06:47] schestowitz[TR2] - My capacity does not seem to have been calculated correctly. My [06:47] schestowitz[TR2] parental leave/ home leave / unpaid leave/ part-time / [PLANNED [06:47] schestowitz[TR2] MEDICAL INTERVENTION] were not deducted from the total working [06:47] schestowitz[TR2] days. [06:47] schestowitz[TR2] - The many hours expected to be spent in training, (team) meetings, [06:47] schestowitz[TR2] system disturbances, etc which in my case amount to [06:47] schestowitz[TR2] approximately [FILL IN AN ESTIMATON OF THE NUMBER OF DAYS THIS [06:47] schestowitz[TR2] WOULD TAKE YOU] days have also not been taken into consideration; [06:47] schestowitz[TR2] - The working tools have not evolved in a way which could help me [06:47] schestowitz[TR2] increase productivity since 2024 and nothing has changed in the [06:47] schestowitz[TR2] way I am supposed to perform my work since 2024, when my target [06:47] schestowitz[TR2] was [FILL IN YOUR TARGET FOR 2024] [06:47] schestowitz[TR2] - The ratio Search / Actions without point / Grants is influenced [06:47] schestowitz[TR2] by management decisions and/or change of work priority during [06:47] schestowitz[TR2] the year, all of which are beyond my control. [06:47] schestowitz[TR2] - The files in Search/Examination allocated to me could come from [06:47] schestowitz[TR2] technical fields outside my Area of Competence, as it happened [06:47] schestowitz[TR2] already in the past OR as already announced by team manager/ [06:47] schestowitz[TR2] director/ COO. In this case it could take me more time to deliver [06:47] schestowitz[TR2] EPC compliant products. [06:47] schestowitz[TR2] I therefore express strong reservations against the production and [06:47] schestowitz[TR2] productive objectives that are set for me for 2025. Nevertheless, as [06:47] schestowitz[TR2] mentioned above, you may of course, continue to count on me to work [06:47] schestowitz[TR2] to the best of my abilities in 2025, as I always have. [06:47] schestowitz[TR2] Best regards [06:47] schestowitz[TR2] [YOUR NAME] [06:47] schestowitz[TR2] ANNEX 2: how to append document to performance report in SuccessFactors [06:47] schestowitz[TR2] 1) print your email in pdf format [06:47] schestowitz[TR2] 2) go to q/successfactors (via EPO VPN) > top left menu > home > scroll down > [06:47] schestowitz[TR2] performance > click on 2025 performance development for [your name ] > top right of [06:47] schestowitz[TR2] the screen there is an icon with paperclip (see below), click on that and you can [06:47] schestowitz[TR2] append your email in pdf format." ● Jan 20 [07:07] schestowitz[TR2] Re: happy new year [07:07] schestowitz[TR2] > I organized a few things over the break. [07:07] schestowitz[TR2] > [07:07] schestowitz[TR2] > I've heard rumors that the invalidated "judgment" is not the end of the [07:07] schestowitz[TR2] > road and they are still plotting various things against my family and I. [07:07] schestowitz[TR2] > I am curious if you have heard any of this. [07:07] schestowitz[TR2] > [07:07] schestowitz[TR2] > I don't personally waste time on social media looking for every plot and [07:07] schestowitz[TR2] > conspiracy so there may be things that I haven't seen, especially over [07:07] schestowitz[TR2] > the holiday season. [07:07] schestowitz[TR2] I have not heard anything to that effect, plus we focus on the battle from Gulagboy and his masters. ● Jan 20 [09:02] *jacobk has quit (Ping timeout: 2m30s) [09:04] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [09:22] schestowitz[TR2] http://ipkitten.blogspot.com/2025/01/guestpost-referral-broadened-to-have.html?showComment=1737300679112#c939468779842631186 [09:22] -TechBytesBot/#techbytes-ipkitten.blogspot.com | GuestPost: A referral broadened? To have ones cake, to eat it...or not yet to get it (G 1/24) - The IPKat [09:22] schestowitz[TR2] "" [09:22] schestowitz[TR2] It is surprising that the questions referred to the EBA do not mention the principle of the broadest technically sensible interpretation which is well settled in the EPO case law . A very recent illustration is provided in T 1886/22 of 5 Nov 2024, Reason 4.1.5 but there are numerous other recent BOA decisions which apply this principle. Under this rule, the description cannot be used to read an unclaimed limitation into the claim.< [09:22] schestowitz[TR2] br />
    However, the description, complemented by the drawings if any, is used in different ways : to gain understanding of the claim terms ; to ensure the interpretation is technically sensible and the description does not explicitly contradict the broadest interpretation, as the Board did in T 1886/22.

    The description is also to be taken into account when it contains a specific definition for a claim term, su [09:22] schestowitz[TR2] ch as the gathered sheet in EP3074804, the patent monopoly in suit in the referring decision T 439/22. Several decisions have accepted that the patent monopoly may be "its own dictionary." In such a case, it make sense for the specific definition provided by the applicant in the description of the original application to prevail over the ordinary meaning of the term. The applicant should not be allowed to de [09:22] schestowitz[TR2] part from the definition it has itself established in the description, as this would allow the applicant to make use of the famous angora cat game.

    It is of note that UPC CD Paris decision Njoy v Juuls of 5 Nov 2024 have included in their statement of principles regarding claim interpretation the possibility that the patent monopoly may be its own lexicon (see point 7.7). The same is repeated in the UPC CD Pa [09:22] schestowitz[TR2] ris decision of 17 Jan 2025 between the same parties (point 8.7).

    As to the link with the requirement to adapt the description to the claims, raised in the letter of the EPO president to the EBA in G 1/24, attention should be paid to point 7.9 of the Njoy v Juuls decision of 5 Nov 2024 and point 8.9 of the decision of 17 Jan 2025, which state that the description to be considered is that of the original application. If s [09:22] schestowitz[TR2] o, post-filing amendments of the description are irrelevant to claim interpretation. Also of note on the same line : the Hewlett packard v Lama UPC LD Paris of 13 Nov 2024, point 41, in which the court dismissed post-filing amendments of the description." ● Jan 20 [11:25] *schestowitz-TR has quit (Ping timeout: 2m30s) [11:26] *schestowitz-TR has quit (Ping timeout: 120 seconds) ● Jan 20 [12:00] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [12:20] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes [12:32] *schestowitz-TR (~acer-box@freenode/user/schestowitz) has joined #techbytes [12:33] *libertybox2_ (~schestowitz_log@jcfiaarnjjqje.irc) has joined #techbytes [12:33] *libertybox2_ has quit (connection closed) [12:33] *schestowitz-TR (~acer-box@jcfiaarnjjqje.irc) has joined #techbytes [12:33] *Techrights-sec has quit (Ping timeout: 2m30s) [12:33] *logbackup has quit (Ping timeout: 2m30s) [12:33] *Techrights-sec2 has quit (Ping timeout: 2m30s) [12:33] *libertybox2_ (~schestowitz_log@jcfiaarnjjqje.irc) has joined #techbytes [12:33] *techrights-sec1 has quit (Ping timeout: 2m30s) [12:33] *techrights-sec4 has quit (Ping timeout: 2m30s) [12:33] *libertybox2__ (~schestowitz_log@jcfiaarnjjqje.irc) has joined #techbytes [12:33] *libertybox2_ has quit (connection closed) [12:33] *libertybox2__ has quit (connection closed) [12:34] *techrights-sec3 has quit (Ping timeout: 2m30s) [12:35] *techrights-sec4 (~quassel@freenode-vcjae7.ldvb.0amm.hij1op.IP) has joined #techbytes [12:35] *techrights-sec1 (~quassel@jcfiaarnjjqje.irc) has joined #techbytes [12:35] *techrights-sec1 (~quassel@freenode-vcjae7.ldvb.0amm.hij1op.IP) has joined #techbytes [12:35] *techrights-sec4 (~quassel@jcfiaarnjjqje.irc) has joined #techbytes [12:37] *techrights-sec1 has quit (Connection closed) [12:37] *techrights-sec1 has quit (connection closed) [12:40] *techrights-sec4 has quit (Ping timeout: 2m30s) [12:41] *techrights-sec4 has quit (Connection closed) [12:41] *techrights-sec1 (~quassel@jcfiaarnjjqje.irc) has joined #techbytes [12:43] *techrights-sec1 has quit (Ping timeout: 2m30s) [12:45] *techrights-sec1 (~quassel@jcfiaarnjjqje.irc) has joined #techbytes [12:45] *techrights-sec4 (~quassel@jcfiaarnjjqje.irc) has joined #techbytes [12:45] *techrights-sec3 (~quassel@jcfiaarnjjqje.irc) has joined #techbytes [12:45] *316BH4PGI (~quassel@freenode-4hg8qs.ldvb.0amm.hij1op.IP) has joined #techbytes [12:45] *techrights-sec1 (~quassel@freenode-4hg8qs.ldvb.0amm.hij1op.IP) has joined #techbytes [12:46] *techrights-sec4 (~quassel@freenode-4hg8qs.ldvb.0amm.hij1op.IP) has joined #techbytes ● Jan 20 [13:08] *techrights-sec (~quassel@jcfiaarnjjqje.irc) has joined #techbytes [13:10] *techrights-sec2 (~quassel@jcfiaarnjjqje.irc) has joined #techbytes [13:11] *pi_ (~quassel@jcfiaarnjjqje.irc) has joined #techbytes [13:39] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [13:52] *x-amarsh04 has quit (Quit: Konversation terminated!) ● Jan 20 [15:39] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes [15:46] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [15:47] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes ● Jan 20 [16:14] *x-amarsh04 (~amarsh04@yrifiesvn57du.irc) has joined #techbytes [16:16] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [16:17] schestowitz[TR2] > The Register still posting this retrospective MICROS~1 self-serving [16:17] schestowitz[TR2] > propaganda: [16:17] schestowitz[TR2] > We'll cover this shortly [16:44] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes [16:52] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes ● Jan 20 [17:00] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes ● Jan 20 [18:27] *psydroid3 (~psydroid@xg2evud9qdris.irc) has joined #techbytes ● Jan 20 [21:28] *jacobk has quit (Ping timeout: 2m30s) [21:53] *psydroid3 has quit (Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/)